Triple
T26958082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shunet el-Zebib |
E678962
|
entity |
| Predicate | hasOuterWallHeightApprox |
P46326
|
FINISHED |
| Object | up to about 11 meters in places (originally higher) |
—
|
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 11 meters in places (originally higher) | Statement: [Shunet el-Zebib, hasOuterWallHeightApprox, up to about 11 meters in places (originally higher)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOuterWallHeightApprox Context triple: [Shunet el-Zebib, hasOuterWallHeightApprox, up to about 11 meters in places (originally higher)]
-
A.
hasOuterWallWidthApprox
Indicates that an entity has an outer wall whose width is approximately a specified value.
-
B.
hasOuterWallLengthApprox
Indicates that an entity has an outer wall whose length is approximately a specified value.
-
C.
hasOuterWall
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
-
D.
enclosureWallHeight
chosen
Indicates the height of the wall that forms the boundary or enclosure around an area or structure.
-
E.
hasWall
Indicates that one entity possesses, includes, or is bounded by a wall.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 6:28 a.m.