Triple
T1457447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indus Valley |
E31429
|
entity |
| Predicate | earlierOccupation |
P28984
|
FINISHED |
| Object | c. 3300–2600 BCE |
—
|
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: c. 3300–2600 BCE | Statement: [Indus Valley, earlierOccupation, c. 3300–2600 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierOccupation Context triple: [Indus Valley, earlierOccupation, c. 3300–2600 BCE]
-
A.
hadOccupationStatusUntil
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
-
B.
formerEconomicActivity
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
-
C.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
D.
derivesFromOccupation
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
-
E.
parentOccupation
Indicates that one entity has an occupation which is the job or profession of the other entity’s parent.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c598b30c8190b87207adf608b89a |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.