Triple
T16268861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamabe |
E394943
|
entity |
| Predicate | capitalRelocationPolicy |
P25378
|
FINISHED |
| Object | movedImperialCapitalFromNara |
—
|
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: movedImperialCapitalFromNara | Statement: [Yamabe, capitalRelocationPolicy, movedImperialCapitalFromNara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalRelocationPolicy Context triple: [Yamabe, capitalRelocationPolicy, movedImperialCapitalFromNara]
-
A.
capitalMovedFrom
chosen
Indicates that a capital city was relocated from one place (the source) to another (the destination).
-
B.
dateCapitalMoved
Indicates the date on which a capital city was officially relocated from one place to another.
-
C.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
-
D.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
E.
cityRelocationStatus
Indicates the status or stage of a city’s relocation process from one place to another.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245ca5c708190a1e98ab37740c032 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.