Triple
T14136918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xizhimen Gate site |
E350320
|
entity |
| Predicate | cityGateOrientation |
P28310
|
FINISHED |
| Object | western gate |
—
|
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: western gate | Statement: [Xizhimen Gate site, cityGateOrientation, western gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityGateOrientation Context triple: [Xizhimen Gate site, cityGateOrientation, western gate]
-
A.
cityGateTo
Indicates a directional relationship where one location or path leads to or opens into a city gate.
-
B.
cityGateAxisTerminus
Indicates the point or structure where a principal axis or thoroughfare of a city terminates at or aligns with a city gate.
-
C.
cityGatesName
Indicates that a set of city gates bears or is identified by a specific name.
-
D.
gateOrientation
chosen
Indicates the directional alignment or facing direction of a gate relative to a reference frame or coordinate system.
-
E.
hasCityGateFunction
Indicates that something serves the role or function of a city gate, such as controlling access, passage, or boundary between a city and its surroundings.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:28 a.m.