Triple
T15461546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardanger Bridge |
E371911
|
entity |
| Predicate | hasCableType |
P1373
|
FINISHED |
| Object | suspension cables |
—
|
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: suspension cables | Statement: [Hardanger Bridge, hasCableType, suspension cables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCableType Context triple: [Hardanger Bridge, hasCableType, suspension cables]
-
A.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
hasCableArrangement
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
C.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
D.
cableLength
Indicates the physical length of a cable connecting or associated with an entity.
-
E.
hasUSBConnectorType
Indicates the specific type or standard of USB connector associated with a device or component.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.