Triple
T13479217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Bay 3 |
E318326
|
entity |
| Predicate | structuralForm |
P23125
|
FINISHED |
| Object | high-bay vertical integration space |
—
|
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: high-bay vertical integration space | Statement: [High Bay 3, structuralForm, high-bay vertical integration space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralForm Context triple: [High Bay 3, structuralForm, high-bay vertical integration space]
-
A.
structuralExpression
Indicates that one entity represents the structural or formal expression of another, such as a configuration, layout, or organized form that embodies its structure.
-
B.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
C.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
formationType
chosen
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf266c508190930d30776c09ce35 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.