Triple
T30163435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entemena |
E766730
|
entity |
| Predicate | reignInMillennium |
P179234
|
FINISHED |
| Object | 3rd millennium 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: 3rd millennium BCE | Statement: [Entemena, reignInMillennium, 3rd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignInMillennium Context triple: [Entemena, reignInMillennium, 3rd millennium BCE]
-
A.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
B.
reignCenturyBCE
Indicates that a subject’s reign or rule occurred during a specified century before the Common Era (BCE).
-
C.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
D.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
E.
centuryOfReign
Indicates the century during which a given entity’s reign or rule took place.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 29, 2026, 7:22 p.m.