Triple
T27818754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate Gulch, Montana |
E702753
|
entity |
| Predicate | majorCamp |
P191963
|
FINISHED |
| Object | Diamond City, Montana |
—
|
NE NERFINISHED |
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: Diamond City, Montana | Statement: [Confederate Gulch, Montana, majorCamp, Diamond City, Montana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCamp Context triple: [Confederate Gulch, Montana, majorCamp, Diamond City, Montana]
-
A.
majorSee
Indicates that one entity serves as the primary or most important location where another entity is based, operates, or is centered.
-
B.
major
Indicates that one entity is the primary field of academic specialization or main area of study for another entity.
-
C.
majorFor
Indicates that an academic program, field of study, or specialization is the primary major associated with a particular student or degree.
-
D.
majorSchool
Indicates that one entity is the primary or most significant school or educational institution associated with another entity.
-
E.
majorTeam
Indicates that one entity is the primary or most significant team associated with another entity (such as a person, event, or organization).
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: April 27, 2026, 5:47 p.m.