Triple
T30874370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of the Woman |
E786433
|
entity |
| Predicate | rotationMechanism |
P7284
|
FINISHED |
| Object | pivot near one end of the central 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: pivot near one end of the central span | Statement: [Bridge of the Woman, rotationMechanism, pivot near one end of the central span]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationMechanism Context triple: [Bridge of the Woman, rotationMechanism, pivot near one end of the central span]
-
A.
hasRotationMechanic
Indicates that the subject includes or supports a gameplay or functional mechanic involving rotation or turning as a core interaction.
-
B.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
C.
rotationProcess
Indicates a process in which something is turned or rotated around an axis or point over time.
-
D.
rotationType
chosen
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
E.
tiltingMechanism
Indicates a relationship where one entity serves as a mechanism that enables another entity to tilt or be tilted.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d56ec081909265c4b014388243 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.