Triple
T21541448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Shrine |
E531498
|
entity |
| Predicate | firstTraditionalConstructionDate |
P103773
|
FINISHED |
| Object | Kofun period |
—
|
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: Kofun period | Statement: [Inner Shrine, firstTraditionalConstructionDate, Kofun period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTraditionalConstructionDate Context triple: [Inner Shrine, firstTraditionalConstructionDate, Kofun period]
-
A.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
B.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
C.
oldestBuildingDate
Indicates the calendar date on which the earliest or first-constructed building in a given set or area was built or completed.
-
D.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
E.
claimedConstructionDate
chosen
Indicates the date on which an entity is asserted or reported to have been constructed, according to some claim or source.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d12b264819096f844b5833198aa |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.