Triple
T5420339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hamilton |
E121232
|
entity |
| Predicate | usedByNotablePersonsInField |
P37984
|
FINISHED |
| Object | politics |
—
|
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: politics | Statement: [John Hamilton, usedByNotablePersonsInField, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByNotablePersonsInField Context triple: [John Hamilton, usedByNotablePersonsInField, politics]
-
A.
borneByNotablePeopleInField
Indicates that something (such as a name, title, or distinction) is carried or held by individuals who are recognized as notable within a particular field.
-
B.
usedByNotablePerson
chosen
Indicates that something is or has been used by a person who is widely recognized or notable.
-
C.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
D.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
E.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87e8f1cc81908b997f8a417697c0 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.