Triple
T37648576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-123 Provider |
E937106
|
entity |
| Predicate | specializedMission |
P22637
|
FINISHED |
| Object | aerial spraying of herbicides |
—
|
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: aerial spraying of herbicides | Statement: [C-123 Provider, specializedMission, aerial spraying of herbicides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specializedMission Context triple: [C-123 Provider, specializedMission, aerial spraying of herbicides]
-
A.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
tertiaryMission
Indicates a relationship where an entity has a third-level or lower-priority mission or objective in addition to its primary and secondary missions.
-
C.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
D.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
-
E.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:18 p.m.