Triple
T7629795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone Lanterns |
E172730
|
entity |
| Predicate | placedAlong |
P2409
|
FINISHED |
| Object | temple approach paths |
—
|
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: temple approach paths | Statement: [Stone Lanterns, placedAlong, temple approach paths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placedAlong Context triple: [Stone Lanterns, placedAlong, temple approach paths]
-
A.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
B.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
C.
definedAlong
Indicates that one entity is specified, established, or determined in relation to the course, boundary, or extent of another entity.
-
D.
collocatedWith
Indicates that two entities are located in the same place or spatial context at the same time.
-
E.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.