Triple
T5535357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinus Nijhoff Bridge |
E145147
|
entity |
| Predicate | hasCables |
P1373
|
FINISHED |
| Object | steel stay 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: steel stay cables | Statement: [Martinus Nijhoff Bridge, hasCables, steel stay cables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCables Context triple: [Martinus Nijhoff Bridge, hasCables, steel stay cables]
-
A.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
B.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
C.
requiresContinuousCableRun
Indicates that the relationship or action can only be fulfilled if there is an unbroken, end-to-end cable connection between the involved entities.
-
D.
hasCouplers
Indicates that one entity is equipped with or possesses couplers that enable it to connect or link to another entity.
-
E.
cableEnd
Indicates that one entity represents an endpoint or terminal position of a cable in relation to another entity.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01faed1d08190b6a57faedaf1b56a |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.