Triple
T26099351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Mongol Shahnama |
E658352
|
entity |
| Predicate | partHeldIn |
P160718
|
FINISHED |
| Object | Khalili Collection |
—
|
NE NERFINISHED |
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: Khalili Collection | Statement: [Great Mongol Shahnama, partHeldIn, Khalili Collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partHeldIn Context triple: [Great Mongol Shahnama, partHeldIn, Khalili Collection]
-
A.
partHeldIn
chosen
Indicates that a component or part is physically contained or secured within another object or structure.
-
B.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
C.
sometimesHeldBy
Indicates that one entity is occasionally or intermittently possessed, owned, or physically held by another entity, but not on a constant or permanent basis.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 7:53 p.m.