Triple
T34580999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hikawa Shrine (Ōmiya) |
E887900
|
entity |
| Predicate | hasApproachLength |
P194433
|
FINISHED |
| Object | approximately 2 km |
—
|
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: approximately 2 km | Statement: [Hikawa Shrine (Ōmiya), hasApproachLength, approximately 2 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachLength Context triple: [Hikawa Shrine (Ōmiya), hasApproachLength, approximately 2 km]
-
A.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
B.
hasApproachStructure
Indicates that one entity possesses or includes an approach structure that provides access or a path leading to another entity.
-
C.
hasApproachFeature
Indicates that something possesses a characteristic, element, or quality specifically related to its method, strategy, or manner of approach.
-
D.
hasApproachTime
Indicates that an entity is associated with a specific time at which it approaches or comes near another entity or location.
-
E.
hasApproachSpans
Indicates that one structure or element includes or is associated with approach spans leading into or out of it.
- F. None of above. chosen
Provenance (4 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 1, 2026, 2:03 a.m.