Triple
T22008056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Lead of Ohio |
E543501
|
entity |
| Predicate | servedProgram |
P146254
|
FINISHED |
| Object | U.S. nuclear weapons complex |
—
|
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: U.S. nuclear weapons complex | Statement: [National Lead of Ohio, servedProgram, U.S. nuclear weapons complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedProgram Context triple: [National Lead of Ohio, servedProgram, U.S. nuclear weapons complex]
-
A.
servesProgram
Indicates that one entity provides services or functions in support of a particular program.
-
B.
intendedProgram
Indicates the academic or training program that an entity plans or expects to pursue, rather than one they are currently enrolled in or have completed.
-
C.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
D.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
E.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
- F. None of above. chosen
Provenance (4 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a2aebc8190951ee0bf9fd8e16d |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:21 p.m.