Triple
T23917044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Wall (Jerusalem) |
E602110
|
entity |
| Predicate | heightPreserved |
P9788
|
FINISHED |
| Object | up to about 3.3 meters |
—
|
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: up to about 3.3 meters | Statement: [Broad Wall (Jerusalem), heightPreserved, up to about 3.3 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightPreserved Context triple: [Broad Wall (Jerusalem), heightPreserved, up to about 3.3 meters]
-
A.
originalHeight
Indicates the initial or starting height of an entity before any change, adjustment, or transformation occurs.
-
B.
marginPreservedIn
Indicates that the margin or boundary of an object, area, or content is maintained unchanged within a specified context or container.
-
C.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
heightContext
Indicates a contextual or situational relationship that specifies how an entity’s height is defined, measured, or interpreted in a particular setting or frame of reference.
-
E.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce9a744c819080bd30176b8de9a0 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:40 p.m.