Triple
T11814812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrmont Bridge |
E280969
|
entity |
| Predicate | swingMechanismType |
P30005
|
FINISHED |
| Object | electric motor-driven swing span |
—
|
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: electric motor-driven swing span | Statement: [Pyrmont Bridge, swingMechanismType, electric motor-driven swing span]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swingMechanismType Context triple: [Pyrmont Bridge, swingMechanismType, electric motor-driven swing span]
-
A.
hingeType
Indicates the specific kind or configuration of hinge mechanism that connects two parts or surfaces.
-
B.
openingMechanism
chosen
Indicates the method or mechanism by which an object or structure is opened or made accessible.
-
C.
tiltingMechanism
Indicates a relationship where one entity serves as a mechanism that enables another entity to tilt or be tilted.
-
D.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
escapementType
Indicates the specific mechanism or method by which motion or energy is intermittently released or regulated in a 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.