Triple
T22908571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan Buddhist altar |
E568517
|
entity |
| Predicate | hasOrientationRule |
P141529
|
FINISHED |
| Object | often faces east |
—
|
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: often faces east | Statement: [Tibetan Buddhist altar, hasOrientationRule, often faces east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrientationRule Context triple: [Tibetan Buddhist altar, hasOrientationRule, often faces east]
-
A.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
B.
hasOrientationInUse
chosen
Indicates that an entity, when in use or operation, is oriented in a specific direction or spatial alignment.
-
C.
hasRegionalOrientation
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
-
D.
hasPolicyOrientation
Indicates that one entity (such as an organization, document, or actor) is characterized by or aligned with a particular policy stance, direction, or focus.
-
E.
hasStripeOrientation
Indicates the directional arrangement or alignment of stripes present on an entity.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18072986881909eefb317ced5a145 |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.