Triple
T14170513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menominee |
E351192
|
entity |
| Predicate | experiencedPolicy |
P26998
|
FINISHED |
| Object | termination policy of the United States |
—
|
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: termination policy of the United States | Statement: [Menominee, experiencedPolicy, termination policy of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedPolicy Context triple: [Menominee, experiencedPolicy, termination policy of the United States]
-
A.
policyExperienced
chosen
Indicates that an entity has undergone, been subject to, or directly encountered a particular policy.
-
B.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
C.
advancedPolicyOf
Indicates that one policy is a more developed, detailed, or progressive version of another policy.
-
D.
experiencedProcess
Indicates that an entity has undergone or participated in a particular process or event.
-
E.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
- 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_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. |
Created at: April 10, 2026, 1:01 a.m.