Triple
T24996111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islington Tunnel |
E625571
|
entity |
| Predicate | laterBoatPropulsion |
P59116
|
FINISHED |
| Object | mechanical tugs |
—
|
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: mechanical tugs | Statement: [Islington Tunnel, laterBoatPropulsion, mechanical tugs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBoatPropulsion Context triple: [Islington Tunnel, laterBoatPropulsion, mechanical tugs]
-
A.
boatPower
Indicates a relationship where a boat is characterized by or associated with a specific power rating or propulsion strength.
-
B.
laterPropulsion
chosen
Indicates that one propulsion system, method, or event occurs after another in time.
-
C.
auxiliaryPropulsion
Indicates that an entity provides secondary or backup propulsion support to another entity or system.
-
D.
currentPropulsionSystem
Indicates the propulsion system that an entity is presently using or equipped with.
-
E.
familyPropulsion
Indicates a relationship where one family member drives, motivates, or pushes another family member toward action, change, or progress.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:04 a.m.