Triple
T33837011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gate of Stability |
E867259
|
entity |
| Predicate | cityWallSystem |
P151454
|
FINISHED |
| Object | Ming-era Beijing city wall |
—
|
NE NERFINISHED |
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: Ming-era Beijing city wall | Statement: [Gate of Stability, cityWallSystem, Ming-era Beijing city wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWallSystem Context triple: [Gate of Stability, cityWallSystem, Ming-era Beijing city wall]
-
A.
cityWallType
Indicates the type or classification of a city wall associated with a given place or structure.
-
B.
cityWallRelation
chosen
Indicates a structural or spatial relationship between a city and its surrounding wall, such as presence, connection, or association.
-
C.
hasCityWallFunction
Indicates that an entity serves the functional role of a city wall, such as providing defense, enclosure, or boundary protection for an urban area.
-
D.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
E.
hasCityWallOrientation
Indicates the directional orientation or alignment of a city’s defensive wall relative to cardinal or geographic directions.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7002f38308190af948b97a35a5b09 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.