Triple
T36557174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcho |
E901727
|
entity |
| Predicate | ledMigrationAcross |
P47250
|
FINISHED |
| Object | River Baranduin |
—
|
NE NERFINISHED |
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: River Baranduin | Statement: [Marcho, ledMigrationAcross, River Baranduin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledMigrationAcross Context triple: [Marcho, ledMigrationAcross, River Baranduin]
-
A.
enabledMigrationOf
chosen
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
B.
migratedAcross
Indicates movement of an entity from one side of a boundary, region, or area to the other, typically implying a significant relocation or crossing.
-
C.
verticalMigration
Indicates movement of an entity up and down along a vertical axis, typically in a repeated or cyclical pattern over time.
-
D.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
E.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.