Triple
T26773710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Pearson |
E670055
|
entity |
| Predicate | roleInPearson |
P189417
|
FINISHED |
| Object | Chicago political fixer |
—
|
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: Chicago political fixer | Statement: [Jessica Pearson, roleInPearson, Chicago political fixer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPearson Context triple: [Jessica Pearson, roleInPearson, Chicago political fixer]
-
A.
courseRole
Indicates the specific function or position an individual holds within a course, such as student, instructor, or assistant.
-
B.
hasEducationalRole
Indicates that an entity holds a specific function, position, or responsibility within an educational context or setting.
-
C.
educationalRoleSince
Indicates the point in time since which an entity has held a particular educational role or position in relation to another entity.
-
D.
roleInClass
Indicates the specific function, position, or responsibility an entity holds within a particular class or group.
-
E.
roleAtInstructure
Indicates that an entity holds a specific role or position within the organization Instructure.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 27, 2026, 4:03 a.m.