Triple
T12432978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Johnson |
E297076
|
entity |
| Predicate | isAmericanPolitician |
P104904
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mike Johnson, isAmericanPolitician, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmericanPolitician Context triple: [Mike Johnson, isAmericanPolitician, true]
-
A.
isPoliticalOffice
Indicates that the subject is a formal governmental or political position held within a public institution or authority.
-
B.
hasPoliticalPositionOn
Indicates that an entity holds or expresses a specific stance, view, or opinion regarding a political issue, policy, or topic.
-
C.
notablePolitician
Indicates that the subject is a politician who is recognized as notable or significant in a political context.
-
D.
hasUSSenator
Indicates that a specified state or jurisdiction is represented by a particular individual serving as a United States Senator.
-
E.
notableLivingRepresentative
Indicates that one entity is a prominent currently-living example or representative of another entity (such as a group, category, or organization).
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94df652cc8190a1d2d685fa87cf98 |
completed | April 10, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:55 p.m.