Triple
T32520544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOD |
E831168
|
entity |
| Predicate | usedInGovernmentCommunication |
P5304
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [FOD, usedInGovernmentCommunication, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInGovernmentCommunication Context triple: [FOD, usedInGovernmentCommunication, yes]
-
A.
usedInGovernmentIn
Indicates that something is employed, applied, or functions within the context of a specific government or governmental system.
-
B.
usedGovernmentSystem
Indicates that an entity employed or operated under a particular form or system of government.
-
C.
includeGovernmentOf
Indicates that one entity contains, encompasses, or incorporates the government of another entity as part of its structure or scope.
-
D.
usedInDigitalCommunication
Indicates that something is employed as a medium, tool, or element within digital or electronic communication processes.
-
E.
usedInOfficialDocumentsOf
chosen
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or jurisdiction.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 1 a.m.