Triple
T16934231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sufi orders |
E410787
|
entity |
| Predicate | oftenHave |
P124802
|
FINISHED |
| Object | lodges |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: lodges | Statement: [Sufi orders, oftenHave, lodges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHave Context triple: [Sufi orders, oftenHave, lodges]
-
A.
oftenUse
Indicates that one entity frequently or regularly uses, employs, or utilizes another entity.
-
B.
wereOften
Indicates that the related entities frequently or repeatedly exhibited the specified state, behavior, or relationship in the past.
-
C.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
D.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
-
E.
oftenAccompaniedBy
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2714b08190a2524d5d9578cc87 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.