Triple
T4021954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Palo Alto |
E91297
|
entity |
| Predicate | hasStructuralSupport |
P18077
|
FINISHED |
| Object | cables and braces |
—
|
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: cables and braces | Statement: [El Palo Alto, hasStructuralSupport, cables and braces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructuralSupport Context triple: [El Palo Alto, hasStructuralSupport, cables and braces]
-
A.
supportsStructure
chosen
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
B.
supportStructureFor
Indicates that one entity serves as a physical or functional support structure for another entity.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasDependentSupport
Indicates that one entity provides financial or material support for another entity who is recognized as a dependent.
-
E.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.