Triple
T26885441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Milner |
E677028
|
entity |
| Predicate | nameBearersIncludeField |
P2531
|
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: [George Milner, nameBearersIncludeField, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearersIncludeField Context triple: [George Milner, nameBearersIncludeField, politics]
-
A.
typicalNameBearers
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
-
B.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
C.
hasNotableFieldOfBearers
chosen
Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
-
D.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
E.
nameBearersUsuallyHaveLegalName
Indicates that entities which bear a certain name typically also possess that name as their official legal name.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:41 a.m.