Triple
T9924057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Adobe Walls (1874) |
E187875
|
entity |
| Predicate | foughtOver |
P50503
|
FINISHED |
| Object | control of buffalo 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: control of buffalo hunting grounds | Statement: [Battle of Adobe Walls (1874), foughtOver, control of buffalo hunting grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtOver Context triple: [Battle of Adobe Walls (1874), foughtOver, control of buffalo hunting grounds]
-
A.
fought
Indicates that one entity engaged in physical or armed conflict or combat against another entity.
-
B.
wasContestedBetween
chosen
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
E.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb59733188190900426e4e29ae5e3 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.