Triple
T21300447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagaoka-kyō |
E525046
|
entity |
| Predicate | timeInUseAsCapital |
P20655
|
FINISHED |
| Object | about 10 years |
—
|
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: about 10 years | Statement: [Nagaoka-kyō, timeInUseAsCapital, about 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUseAsCapital Context triple: [Nagaoka-kyō, timeInUseAsCapital, about 10 years]
-
A.
usedCapital
Indicates that an entity made use of a particular capital city as its seat of government or primary administrative center.
-
B.
timeAsCapital
chosen
Indicates the period during which a particular city served as the capital of a political entity.
-
C.
usedCapitalAs
Indicates that one entity employed another entity as financial capital or funding in carrying out an action or achieving a result.
-
D.
timeAsCapitalStart
Indicates the point in time when a location first became the capital of a political or administrative entity.
-
E.
capitalUse
Indicates the use or application of financial capital by one entity in relation to another entity or activity.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385c078881908a451be1a19a64c5 |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.