Triple
T354857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Cod Canal Railroad Bridge |
E7520
|
entity |
| Predicate | hasLiftMechanism |
P8166
|
FINISHED |
| Object | counterweight system |
—
|
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: counterweight system | Statement: [Cape Cod Canal Railroad Bridge, hasLiftMechanism, counterweight system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiftMechanism Context triple: [Cape Cod Canal Railroad Bridge, hasLiftMechanism, counterweight system]
-
A.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
-
B.
hasBaggageSystem
Indicates that an entity is equipped with or utilizes a baggage handling system.
-
C.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
-
D.
landingGearType
Indicates the specific kind or configuration of landing gear that an object (typically an aircraft or vehicle) uses.
-
E.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb8312f4819084dc222e665fded3 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.