Triple
T14170515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menominee |
E351192
|
entity |
| Predicate | terminationEndedIn |
P113094
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [Menominee, terminationEndedIn, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminationEndedIn Context triple: [Menominee, terminationEndedIn, 1973]
-
A.
typicallyTerminatedIn
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
B.
terminationPolicyEnded
Indicates that a previously established termination policy has come to an end and is no longer in effect.
-
C.
terminationMechanism
Indicates the process or method by which an ongoing state, activity, or relationship is brought to an end.
-
D.
terminationCondition
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
E.
terminalCondition
Indicates the condition or set of conditions under which a process, interaction, or state is considered complete and should terminate.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:01 a.m.