Triple
T25415563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallace Wooley |
E636822
|
entity |
| Predicate | hasPoliticalImage |
P164987
|
FINISHED |
| Object | upright public figure |
—
|
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: upright public figure | Statement: [Wallace Wooley, hasPoliticalImage, upright public figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalImage Context triple: [Wallace Wooley, hasPoliticalImage, upright public figure]
-
A.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
B.
hasPoliticalComponent
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
C.
hasPoliticalCurrent
Indicates that an entity is associated with, aligned to, or characterized by a particular political current, ideology, or movement.
-
D.
usedAsPoliticalPawnBy
Indicates that one entity is manipulated or exploited by another for political advantage or strategic political purposes.
-
E.
hasPoliticalPositionOn
Indicates that an entity holds or expresses a specific stance, view, or opinion regarding a political issue, policy, or topic.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 21, 2026, 1:55 p.m.