Triple
T8147264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klyde Warren |
E190244
|
entity |
| Predicate | hasNotabilityType |
P33147
|
FINISHED |
| Object | eponym of public park |
—
|
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: eponym of public park | Statement: [Klyde Warren, hasNotabilityType, eponym of public park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotabilityType Context triple: [Klyde Warren, hasNotabilityType, eponym of public park]
-
A.
hasNotabilityCategory
Indicates that an entity is associated with a particular category that characterizes its type or area of notability.
-
B.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
C.
hasNotableType
chosen
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasNotabilitySource
Indicates that there exists an external, recognized source that attests to or supports the notability or significance of the subject entity.
-
E.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb447d6b1881908ff3fa25af6b4e80 |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.