Triple
T25006168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Floating Market |
E625845
|
entity |
| Predicate | movesThrough |
P30219
|
FINISHED |
| Object | disused stations and hidden places |
—
|
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: disused stations and hidden places | Statement: [The Floating Market, movesThrough, disused stations and hidden places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movesThrough Context triple: [The Floating Market, movesThrough, disused stations and hidden places]
-
A.
movementAcross
chosen
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
-
B.
movesBeyond
Indicates that one entity changes position so as to pass further than or outside the limits of another reference point, object, or boundary.
-
C.
movesFrom
Indicates that an entity changes location by departing or originating from a specified place.
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
E.
moves
Indicates that an entity changes its position or location over time, typically from one place to another.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:05 a.m.