Triple
T34989334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shady Sands region |
E1009336
|
entity |
| Predicate | securityForcesInLore |
P44512
|
FINISHED |
| Object | NCR militia |
—
|
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: NCR militia | Statement: [Shady Sands region, securityForcesInLore, NCR militia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityForcesInLore Context triple: [Shady Sands region, securityForcesInLore, NCR militia]
-
A.
strengthGovernmentForces
Indicates the level or degree of military or coercive power held or exerted by government forces in a given context.
-
B.
defenseForces
chosen
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
-
C.
securityTowns
Indicates a relationship where certain towns are designated, managed, or treated in terms of their security status, measures, or responsibilities.
-
D.
safetyInFiction
Indicates that a work of fiction portrays conditions, measures, or themes related to safety, risk, or protection within its narrative world.
-
E.
securityFigure
Indicates that one entity serves as a protective or safeguarding presence for another, typically responsible for ensuring its safety or security.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.