Triple
T14294475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dromeian Chapter |
E354401
|
entity |
| Predicate | isCustomOrFanCreated |
P113657
|
FINISHED |
| Object | likely |
—
|
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: likely | Statement: [Dromeian Chapter, isCustomOrFanCreated, likely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCustomOrFanCreated Context triple: [Dromeian Chapter, isCustomOrFanCreated, likely]
-
A.
hasServingCustom
Indicates that an entity follows or applies a particular custom, style, or convention in how something (such as food, drink, or service) is served.
-
B.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
C.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
D.
isPurchasedBy
Indicates that one entity is bought or acquired in a transaction by another entity.
-
E.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717b35ec81908968994e65737c66 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.