Triple
T31059412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower of the Five Orders |
E791488
|
entity |
| Predicate | hasNumberOfArchitecturalOrders |
P194613
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Tower of the Five Orders, hasNumberOfArchitecturalOrders, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfArchitecturalOrders Context triple: [Tower of the Five Orders, hasNumberOfArchitecturalOrders, 5]
-
A.
architecturalOrderUsed
Indicates that a particular architectural order (e.g., Doric, Ionic, Corinthian) is employed in the design or construction of a structure or its elements.
-
B.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
hasNumberOfArches
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
D.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
E.
mainArchitecturalForm
Indicates the primary architectural style or structural form that characterizes a building or construction.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: April 29, 2026, 9 p.m.