Triple
T29021409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Palace |
E737459
|
entity |
| Predicate | capitalOfEmpireContext |
P11792
|
FINISHED |
| Object | Neo-Assyrian 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: Neo-Assyrian Empire | Statement: [North Palace, capitalOfEmpireContext, Neo-Assyrian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfEmpireContext Context triple: [North Palace, capitalOfEmpireContext, Neo-Assyrian Empire]
-
A.
administrativeCenterForEmpire
chosen
Indicates that a location served as the main administrative center or capital for a particular empire.
-
B.
capitalOfCountryRuled
Indicates that a city serves as the capital of a country that is (or was) governed by a specified ruler or ruling entity.
-
C.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
D.
capitalCityDuringEra
Indicates that a particular city served as the capital of an entity (such as a country or region) during a specified historical era or time period.
-
E.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 9:49 a.m.