Triple
T24243172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Emmanuel |
E603286
|
entity |
| Predicate | positionWithinMovement |
P21941
|
FINISHED |
| Object | prominent leader |
—
|
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: prominent leader | Statement: [King Emmanuel, positionWithinMovement, prominent leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinMovement Context triple: [King Emmanuel, positionWithinMovement, prominent leader]
-
A.
positionInMovement
Indicates the specific role or placement an entity holds within a broader movement or collective action.
-
B.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
movementStatus
Indicates the current state or condition of an entity’s movement, such as whether and how it is moving or stationary.
-
E.
roleInMovement
chosen
Indicates the specific function, position, or contribution an entity has within a broader movement or collective effort.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28aa1309c8190b9bc33bc6598b0fc |
completed | April 29, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.