Triple
T8100366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Interlocking |
E189092
|
entity |
| Predicate | signalingType |
P4618
|
FINISHED |
| Object | interlocking signal system |
—
|
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: interlocking signal system | Statement: [Harold Interlocking, signalingType, interlocking signal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalingType Context triple: [Harold Interlocking, signalingType, interlocking signal system]
-
A.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
B.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
D.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
E.
compatibleWithSignaling
Indicates that one entity can correctly interpret, process, or operate using the signaling mechanisms, protocols, or formats employed by 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42ba9af88190b6310d799818e3d5 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:31 p.m.