Triple
T37872485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shado-Pan Monastery |
E944639
|
entity |
| Predicate | entranceCoordinatesApprox |
P189940
|
FINISHED |
| Object | 36, 47 |
—
|
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: 36, 47 | Statement: [Shado-Pan Monastery, entranceCoordinatesApprox, 36, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceCoordinatesApprox Context triple: [Shado-Pan Monastery, entranceCoordinatesApprox, 36, 47]
-
A.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
B.
corridorStartApprox
Indicates an approximate or estimated starting point of a corridor in relation to another spatial element or reference.
-
C.
isNearEntrance
Indicates that an entity is located close to the entrance of a place or structure.
-
D.
distanceToTheEntrance
Indicates the spatial distance between a given entity and the entrance of a specified place or structure.
-
E.
corridorEndApprox
Indicates that one location is approximately at or near the end of a corridor relative to another location.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:19 p.m.