Triple
T14775989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marble Arch |
E347260
|
entity |
| Predicate | hasCentralArchWidth |
P37680
|
FINISHED |
| Object | approximately 30 feet |
—
|
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 30 feet | Statement: [Marble Arch, hasCentralArchWidth, approximately 30 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralArchWidth Context triple: [Marble Arch, hasCentralArchWidth, approximately 30 feet]
-
A.
centralArchWidth
chosen
Indicates the measured width of the central arch in a structure or object.
-
B.
hasSideArch
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
C.
centralArchHeight
Indicates the vertical height of the central arch in a structure relative to a reference level.
-
D.
hasCentralAxis
Indicates that one entity serves as the primary central axis or line of symmetry around which another entity is organized, aligned, or structured.
-
E.
widthOfArches
Indicates the measurement of how wide the arches are in a given structure or context.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec815dd5081909e927911c06b2d66 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.