Triple
T14542605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SWATH |
E341206
|
entity |
| Predicate | hasSuperstructureSupport |
P18077
|
FINISHED |
| Object | narrow struts |
—
|
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: narrow struts | Statement: [SWATH, hasSuperstructureSupport, narrow struts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperstructureSupport Context triple: [SWATH, hasSuperstructureSupport, narrow struts]
-
A.
hasSuperstructurePosition
Indicates the relative location or placement of a component or element within the superstructure of an object or system.
-
B.
supportsStructure
chosen
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
C.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
-
D.
hasSuperstructureColor
Indicates that one entity has a superstructure whose color is the value specified by the other entity.
-
E.
superstructureType
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1be5a8081909bf727e28a5bba4a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.