Triple
T22308963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swing Bridge |
E551461
|
entity |
| Predicate | canRotate |
P56077
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Swing Bridge, canRotate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRotate Context triple: [Swing Bridge, canRotate, yes]
-
A.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
-
B.
isRotational
chosen
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
C.
hasRotationMechanic
Indicates that the subject includes or supports a gameplay or functional mechanic involving rotation or turning as a core interaction.
-
D.
rotatesWith
Indicates that two or more entities turn or spin together in a coordinated or mechanically linked manner, typically sharing the same rotational motion or axis.
-
E.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574c8a248190bf5eef5be78381fd |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.