Triple
T32350513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson Hummingbird |
E826579
|
entity |
| Predicate | bridgePinsMaterial |
P52395
|
FINISHED |
| Object | plastic or bone depending on model |
—
|
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: plastic or bone depending on model | Statement: [Gibson Hummingbird, bridgePinsMaterial, plastic or bone depending on model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgePinsMaterial Context triple: [Gibson Hummingbird, bridgePinsMaterial, plastic or bone depending on model]
-
A.
bridgeMaterial
chosen
Indicates that a bridge is constructed from, or primarily composed of, a specified material.
-
B.
bridgeComponent
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
-
C.
bridgeModel
Indicates a relationship where one entity serves as an intermediate model or representation that connects or translates between two other entities or systems.
-
D.
bridgeColor
Indicates the color attribute associated with a given bridge.
-
E.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:49 a.m.