Triple
T12705500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Hole (Dahab) |
E303574
|
entity |
| Predicate | archDepthAtRoof |
P106440
|
FINISHED |
| Object | about 52 to 56 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: about 52 to 56 meters | Statement: [Blue Hole (Dahab), archDepthAtRoof, about 52 to 56 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archDepthAtRoof Context triple: [Blue Hole (Dahab), archDepthAtRoof, about 52 to 56 meters]
-
A.
roofHeight
Indicates the vertical distance or elevation of a roof relative to a reference level or structure.
-
B.
roofLevel
Indicates the vertical level or story of a building at which the roof is located or begins.
-
C.
architecturalHeight
Indicates the measured vertical extent of a structure based on its architectural design, typically from the lowest significant level to the highest architecturally integral point, excluding non-architectural elements like antennas or masts.
-
D.
hasRoofShape
Indicates that one entity possesses or is characterized by a specific shape or form of roof.
-
E.
roofCount
Indicates the number of distinct roofs associated with an entity (such as a building or structure).
- F. None of above. chosen
Provenance (4 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96297b81c819081ad1432dc5f15f4 |
completed | April 10, 2026, 8:50 p.m. |
Created at: April 9, 2026, 5:23 p.m.