Triple
T9162325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grantham Canal |
E219854
|
entity |
| Predicate | wasEngineeredFor |
P8196
|
FINISHED |
| Object | horse-drawn boats |
—
|
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: horse-drawn boats | Statement: [Grantham Canal, wasEngineeredFor, horse-drawn boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEngineeredFor Context triple: [Grantham Canal, wasEngineeredFor, horse-drawn boats]
-
A.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
isBuiltFor
chosen
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
badgeEngineeredFrom
Indicates that a badge is derived, created, or generated based on another underlying source, design, or system.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2c1a9881909b7100b6e436386d |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.