Triple
T9264331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge Baby |
E222657
|
entity |
| Predicate | linkedDevice |
P13458
|
FINISHED |
| Object | odradek scanner |
—
|
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: odradek scanner | Statement: [Bridge Baby, linkedDevice, odradek scanner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDevice Context triple: [Bridge Baby, linkedDevice, odradek scanner]
-
A.
relatedDevice
chosen
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
B.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
C.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
D.
linkedInstrument
Indicates that one entity is associated with or connected to another as a related or corresponding instrument.
-
E.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0748a1f481909d9d876692cefccc |
completed | April 1, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.