Triple
T2368203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori sovereignty movement |
E46030
|
entity |
| Predicate | gainedMomentumIn |
P37821
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Māori sovereignty movement, gainedMomentumIn, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedMomentumIn Context triple: [Māori sovereignty movement, gainedMomentumIn, 1970s]
-
A.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
B.
hasMomentumState
Indicates that an entity possesses a particular state or condition related to its momentum (e.g., magnitude, direction, or dynamic status).
-
C.
gainedFrom
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
D.
motivated
Indicates that one entity provides a reason, drive, or incentive that causes another entity to act or behave in a certain way.
-
E.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76bf75c8190b014c3dbfc46bba3 |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6443c6c8190b932de2abd8eb28f |
completed | March 7, 2026, 6:31 a.m. |
Created at: March 4, 2026, 7:56 p.m.