Triple
T24945000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Hill–Glastonbury Ferry |
E624161
|
entity |
| Predicate | previousPropulsion |
P59116
|
FINISHED |
| Object | horse-powered ferry |
—
|
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-powered ferry | Statement: [Rocky Hill–Glastonbury Ferry, previousPropulsion, horse-powered ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPropulsion Context triple: [Rocky Hill–Glastonbury Ferry, previousPropulsion, horse-powered ferry]
-
A.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
B.
laterPropulsion
chosen
Indicates that one propulsion system, method, or event occurs after another in time.
-
C.
currentPropulsionSystem
Indicates the propulsion system that an entity is presently using or equipped with.
-
D.
plannedPropulsionType
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
-
E.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 5:53 a.m.