Triple
T21977695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl L. Brewer |
E542751
|
entity |
| Predicate | notableOfficeLevel |
P146134
|
FINISHED |
| Object | state-level executive |
—
|
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: state-level executive | Statement: [Earl L. Brewer, notableOfficeLevel, state-level executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOfficeLevel Context triple: [Earl L. Brewer, notableOfficeLevel, state-level executive]
-
A.
notableOfficer
Indicates that an entity has served as a significant or distinguished officer of another entity, such as an organization, institution, or group.
-
B.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
C.
notableOfficerRole
Indicates that an entity holds or has held a particularly significant or distinguished officer position within an organization or institution.
-
D.
notableFormerOfficeHolderRole
Indicates that an entity previously held a particular official position or role that is considered notable.
-
E.
notableOfficeStatus
Indicates that an entity holds or has held a particularly significant or distinguished official position or office.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12489889c81909c847cf2f6808d85 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
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:03 p.m.