Triple
T21046007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wainwright |
E518451
|
entity |
| Predicate | hasClassificationRole |
P102097
|
FINISHED |
| Object | defines list of Wainwright fells |
—
|
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: defines list of Wainwright fells | Statement: [Wainwright, hasClassificationRole, defines list of Wainwright fells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassificationRole Context triple: [Wainwright, hasClassificationRole, defines list of Wainwright fells]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
classificationRole
chosen
Indicates that one entity serves as a classificatory role or type used to categorize or group another entity.
-
C.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
D.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf3cac081909915a440fbb5c084 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:33 p.m.