Triple
T37264485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mornington Crescent (game) |
E924345
|
entity |
| Predicate | typicalMove |
P205810
|
FINISHED |
| Object | naming a London Underground station |
—
|
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: naming a London Underground station | Statement: [Mornington Crescent (game), typicalMove, naming a London Underground station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMove Context triple: [Mornington Crescent (game), typicalMove, naming a London Underground station]
-
A.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
B.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
C.
basicMove
Indicates a fundamental movement action performed by or applied to an entity, without specifying any specialized or complex behavior.
-
D.
moves
Indicates that an entity changes its position or location over time, typically from one place to another.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
- F. None of above. chosen
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:15 p.m.