Triple
T3022307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California National Guard |
E82488
|
entity |
| Predicate | typicalStateMissions |
P22637
|
FINISHED |
| Object | wildfire response |
—
|
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: wildfire response | Statement: [California National Guard, typicalStateMissions, wildfire response]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStateMissions Context triple: [California National Guard, typicalStateMissions, wildfire response]
-
A.
numberOfMissions
Indicates the total count of missions associated with a given entity or context.
-
B.
numberOfMemberStateMissions
Indicates the total count of missions associated with or undertaken by the member states in a given context.
-
C.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
D.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
-
E.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a963034819093d96566e9b0cea9 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.