Triple
T32217323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Wykehamist |
E822962
|
entity |
| Predicate | hasNotableFields |
P39276
|
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: [Old Wykehamist, hasNotableFields, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFields Context triple: [Old Wykehamist, hasNotableFields, politics]
-
A.
hasNotableFieldOfDescendant
Indicates that an entity is associated with a notable field or area of expertise specifically through one or more of its descendants.
-
B.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
C.
hasNotableOutput
Indicates that an entity produces or is associated with an output, work, or result that is considered significant or noteworthy.
-
D.
hasNotableFamilyInField
Indicates that an individual has family members who are recognized or distinguished within a particular professional or academic field.
-
E.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
Created at: May 1, 2026, 12:37 a.m.