Triple
T24391383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Johanns |
E614898
|
entity |
| Predicate | followedInOffice |
P131670
|
FINISHED |
| Object | Dale Young |
—
|
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: Dale Young | Statement: [Mike Johanns, followedInOffice, Dale Young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedInOffice Context triple: [Mike Johanns, followedInOffice, Dale Young]
-
A.
officeFollowedInPracticeBy
chosen
Indicates that one office or position is typically succeeded or implemented in practice by another office or position, even if not formally designated as its successor.
-
B.
representsInOffice
Indicates that one entity serves as an official representative of another entity within a specific office, position, or institutional role.
-
C.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
D.
hasRelativeInOffice
Indicates that one entity has a family member who holds or held a particular office or official position.
-
E.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2945878b481909cca6def7b64b42c |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.