Triple
T23638008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmerson |
E583804
|
entity |
| Predicate | hasGivenNameBearerOccupation |
P93726
|
FINISHED |
| Object | politician |
—
|
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: politician | Statement: [Emmerson, hasGivenNameBearerOccupation, politician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenNameBearerOccupation Context triple: [Emmerson, hasGivenNameBearerOccupation, politician]
-
A.
hasNotableBearerOccupation
Indicates that an entity is associated with a notable person who holds a specific occupation.
-
B.
namesakeOccupation
Indicates that one entity’s occupation is the same as, or derived from, the occupation associated with the other entity’s namesake.
-
C.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
D.
occupationOfBearer
chosen
Indicates that a specified occupation or job role is held by the bearer entity.
-
E.
namedAfterOccupationOrRole
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1edccd88190b1d4fc9ec78bc16c |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.