Triple
T13493308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conwy Suspension Bridge |
E320691
|
entity |
| Predicate | hasChainType |
P16808
|
FINISHED |
| Object | eyebar chain |
—
|
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: eyebar chain | Statement: [Conwy Suspension Bridge, hasChainType, eyebar chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChainType Context triple: [Conwy Suspension Bridge, hasChainType, eyebar chain]
-
A.
hasChainFunction
Indicates that an entity possesses or is associated with a specific function or role within a chain or sequence of operations.
-
B.
hasChainCondition
Indicates that one entity is subject to, or satisfies, a specified chain condition imposed or characterized by another entity.
-
C.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
D.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
supportsChain
Indicates that one entity provides the necessary foundation, compatibility, or infrastructure for a particular chain (such as a blockchain or sequence of operations) to function or be used.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4c66008190b287e0551889d7c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.