Triple
T14280722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarchy of the North |
E354037
|
entity |
| Predicate | movementScope |
P113583
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Monarchy of the North, movementScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementScope Context triple: [Monarchy of the North, movementScope, regional]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
movementContext
Indicates the situational or environmental conditions under which a movement or motion event occurs, such as its manner, setting, or constraints.
-
C.
movementDomain
Indicates the general area, medium, or context within which a movement or motion takes place.
-
D.
movementRole
Indicates the specific function or capacity an entity has within a movement or motion-related activity (e.g., mover, path, source, or goal).
-
E.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697b5e8081908e5b91a3a1c55df9 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.