Triple
T3461436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badaling |
E73033
|
entity |
| Predicate | wallWidth |
P619
|
FINISHED |
| Object | approximately 6 meters at the base |
—
|
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: approximately 6 meters at the base | Statement: [Badaling, wallWidth, approximately 6 meters at the base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallWidth Context triple: [Badaling, wallWidth, approximately 6 meters at the base]
-
A.
enclosureWallHeight
Indicates the height of the wall that forms the boundary or enclosure around an area or structure.
-
B.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
-
C.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
D.
width
chosen
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
E.
hasOuterWall
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae745e081909007cd3a664c57f3 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.