Triple
T16281238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | defterdar |
E395266
|
entity |
| Predicate | hadMultipleHolders |
P33660
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [defterdar, hadMultipleHolders, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMultipleHolders Context triple: [defterdar, hadMultipleHolders, yes]
-
A.
hasSuccessiveHolders
Indicates that one entity has a sequence of different entities that have held the same role, position, or status one after another over time.
-
B.
hasBeenHeldBy
Indicates that an entity has previously possessed, controlled, or occupied another entity for some duration in the past.
-
C.
hasMultipleHoldersSimultaneously
chosen
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same time.
-
D.
wasFirstHeldBy
Indicates that an event or activity was initially hosted, organized, or conducted by a particular entity.
-
E.
hasPreviouslyBeenHeldIn
Indicates that an entity was located, confined, or kept in a particular place or container at some time in the past.
- F. None of above.
Provenance (3 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24910c6b881909ae5cc0908dd8eb2 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.