Triple
T923359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Museum, New Delhi |
E19930
|
entity |
| Predicate | collectionPeriodSpan |
P9341
|
FINISHED |
| Object | over 5000 years |
—
|
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: over 5000 years | Statement: [National Museum, New Delhi, collectionPeriodSpan, over 5000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionPeriodSpan Context triple: [National Museum, New Delhi, collectionPeriodSpan, over 5000 years]
-
A.
collectionTimespan
chosen
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
B.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
circulationPeriod
Indicates the length of time during which an item is allowed to be borrowed, used, or remain in active circulation before it must be returned, renewed, or retired.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b314f6fc81908a3ccc2e741e3c2b |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.