Triple
T30354241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huny |
E772101
|
entity |
| Predicate | hasReignPeriod |
P191720
|
FINISHED |
| Object | late 27th century 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: late 27th century BCE | Statement: [Huny, hasReignPeriod, late 27th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReignPeriod Context triple: [Huny, hasReignPeriod, late 27th century BCE]
-
A.
centuryOfReign
Indicates the century during which a given entity’s reign or rule took place.
-
B.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
C.
reignOrLeadershipPeriod
chosen
Indicates the time span during which an entity holds ruling authority or leadership over a group, organization, or territory.
-
D.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
E.
ended reign start year
Indicates the calendar year in which a ruler’s period of reign came to an end.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: April 29, 2026, 7:56 p.m.