Triple
T36830416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty 7 territory |
E910121
|
entity |
| Predicate | preTreatyUse |
P186338
|
FINISHED |
| Object | hunting grounds |
—
|
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: hunting grounds | Statement: [Treaty 7 territory, preTreatyUse, hunting grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preTreatyUse Context triple: [Treaty 7 territory, preTreatyUse, hunting grounds]
-
A.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
-
B.
designedForTreaty
Indicates that something was created or configured specifically to support, implement, or operate under the terms of a particular treaty.
-
C.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
D.
treatyFeature
Indicates that one entity is a characteristic, provision, or specific element that forms part of a treaty.
-
E.
treatyReviewed
Indicates that a treaty has been examined and evaluated, typically for its terms, implications, or compliance, by an authorized party.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:13 p.m.