Triple
T26812319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Nations mandate system |
E672028
|
entity |
| Predicate | notableMandatoryPower |
P199224
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [League of Nations mandate system, notableMandatoryPower, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMandatoryPower Context triple: [League of Nations mandate system, notableMandatoryPower, United Kingdom]
-
A.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
B.
notablePowerType
Indicates that an entity is especially known for possessing or using a particular type of power or ability.
-
C.
majorPowerUntil
Indicates that an entity functioned as a major power or dominant force up to, but not beyond, a specified time or event.
-
D.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
-
E.
notableForce
Indicates that an entity is recognized as a significant or influential force affecting another entity, system, or context.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: April 27, 2026, 4:30 a.m.