Triple
T32190287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Ilia |
E822218
|
entity |
| Predicate | bridgeRole |
P127217
|
FINISHED |
| Object | primary navigator |
—
|
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: primary navigator | Statement: [Lieutenant Ilia, bridgeRole, primary navigator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeRole Context triple: [Lieutenant Ilia, bridgeRole, primary navigator]
-
A.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
B.
bridgeComponent
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
-
C.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
D.
bridgeTunnelRole
chosen
Indicates a functional role that an entity plays specifically in relation to a bridge or tunnel, such as operating, managing, or maintaining it.
-
E.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bacbaa208190b1edec2032701044 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:35 a.m.