Triple
T13837795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pen-y-ghent |
E332574
|
entity |
| Predicate | nameContainsElement |
P96333
|
FINISHED |
| Object | pen |
—
|
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: pen | Statement: [Pen-y-ghent, nameContainsElement, pen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameContainsElement Context triple: [Pen-y-ghent, nameContainsElement, pen]
-
A.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
B.
fullNameIncludes
Indicates that one entity’s full name contains another specified string or name component as a substring.
-
C.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
D.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
-
E.
toponymyContainsElement
chosen
Indicates that a toponym (place name) includes a specific linguistic or semantic element as part of its composition.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ac6b7c81908d44632d6d628339 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.