Triple
T23925400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. politicians |
E602337
|
entity |
| Predicate | operateInSystem |
P41907
|
FINISHED |
| Object | United States government |
—
|
NE NERFINISHED |
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: United States government | Statement: [U.S. politicians, operateInSystem, United States government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operateInSystem Context triple: [U.S. politicians, operateInSystem, United States government]
-
A.
operateIn
chosen
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
C.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
D.
operatedOnSystem
Indicates that an entity has performed operations or actions upon a particular system, affecting its state or behavior.
-
E.
operatorSystem
Indicates a relationship where one entity functions as the operating system that manages or controls another entity (such as a device, application, or system).
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1ce7f88190a4afd091b4384558 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:44 p.m.