Triple
T28808647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuthah |
E727447
|
entity |
| Predicate | politicalEntityDuringAntiquity |
P23483
|
FINISHED |
| Object | Babylonian Empire |
—
|
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: Babylonian Empire | Statement: [Cuthah, politicalEntityDuringAntiquity, Babylonian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalEntityDuringAntiquity Context triple: [Cuthah, politicalEntityDuringAntiquity, Babylonian Empire]
-
A.
countryDuringAntiquity
Indicates that an entity functioned as a country or political territory specifically during the historical period of antiquity.
-
B.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
-
C.
ancientStates
chosen
Indicates that the related entity functioned as a state or political entity in ancient times.
-
D.
ancientPolisCenter
Indicates that a location functioned as the central urban, political, or social hub of an ancient polis (city-state).
-
E.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:30 a.m.