Triple
T4188580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Palace Gate |
E88375
|
entity |
| Predicate | openingDirection |
P28310
|
FINISHED |
| Object | 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: east | Statement: [East Palace Gate, openingDirection, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDirection Context triple: [East Palace Gate, openingDirection, east]
-
A.
openingMechanism
Indicates the method or mechanism by which an object or structure is opened or made accessible.
-
B.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
C.
gateOrientation
chosen
Indicates the directional alignment or facing direction of a gate relative to a reference frame or coordinate system.
-
D.
doorType
Indicates the specific kind or category of door associated with an entity.
-
E.
openingDetail
Indicates the specific manner, context, or characteristics of how an opening (such as a beginning, start, or initial access point) occurs or is carried out between entities.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.