Triple
T34857168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 西楼門 |
E1004757
|
entity |
| Predicate | directionFromShrineCenter |
P187730
|
FINISHED |
| Object | 西側 |
—
|
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: 西側 | Statement: [西楼門, directionFromShrineCenter, 西側]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromShrineCenter Context triple: [西楼門, directionFromShrineCenter, 西側]
-
A.
mainShrineOrientation
Indicates the directional alignment or facing direction of a main shrine relative to a reference point or axis.
-
B.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
C.
possibleShrineLocation
Indicates that a location is suitable or designated as a potential site where a shrine could be placed or constructed.
-
D.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular place or geographic location.
-
E.
orientationWithinTemple
chosen
Indicates the spatial alignment or directional positioning of something relative to the interior layout of a temple.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4 p.m.