Triple
T21778137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pike o’ Blisco |
E537633
|
entity |
| Predicate | hasAscentCharacter |
P145916
|
FINISHED |
| Object | steep |
—
|
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: steep | Statement: [Pike o’ Blisco, hasAscentCharacter, steep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAscentCharacter Context triple: [Pike o’ Blisco, hasAscentCharacter, steep]
-
A.
hasUpperReachesCharacter
Indicates that an entity’s upper reaches or uppermost parts possess a particular characteristic or quality.
-
B.
hasAccentPosition
Indicates the position within a word or phrase where the primary accent or stress is placed.
-
C.
hasVisualCharacter
Indicates that one entity possesses or exhibits a particular visual appearance, style, or graphical characteristic defined by another entity.
-
D.
hasCanonicalCharacter
Indicates that something is associated with or defined by its standard, officially recognized character representation.
-
E.
approximateAscent
Indicates an estimated or non-exact upward change or increase in value, level, or position.
- F. None of above. chosen
Provenance (4 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462b094c81908207073c278a58fe |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.