Triple
T18024217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phimeanakas |
E431203
|
entity |
| Predicate | hasStairOrientation |
P52170
|
FINISHED |
| Object | stairways oriented to cardinal directions |
—
|
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: stairways oriented to cardinal directions | Statement: [Phimeanakas, hasStairOrientation, stairways oriented to cardinal directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStairOrientation Context triple: [Phimeanakas, hasStairOrientation, stairways oriented to cardinal directions]
-
A.
hasStairsFacing
chosen
Indicates that one set of stairs is oriented toward or directly faces another object or direction.
-
B.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
C.
hasStaircaseType
Indicates the specific type or design classification of a staircase associated with an entity.
-
D.
hasStairFunction
Indicates that one entity serves as a stair-related functional feature (e.g., providing access via stairs) for another entity.
-
E.
hasStairName
Indicates that a stairway is associated with a specific name or designation.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c475dc819086c4cd86d663791f |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.