Triple
T4319916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Intelligence, Section 6 |
E96487
|
entity |
| Predicate | overseesArea |
P29031
|
FINISHED |
| Object | foreign intelligence |
—
|
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: foreign intelligence | Statement: [Military Intelligence, Section 6, overseesArea, foreign intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesArea Context triple: [Military Intelligence, Section 6, overseesArea, foreign intelligence]
-
A.
oversawProgramArea
Indicates that one entity had managerial or supervisory responsibility over a specific program area associated with another entity.
-
B.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
-
C.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
D.
assessmentAreaDefinedBy
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
E.
areaAControl
chosen
Indicates that one entity exercises control or authority over a specified area or region.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.