Triple
T37588855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | José Pinzón |
E935200
|
entity |
| Predicate | hasOnomasticNotability |
P175345
|
FINISHED |
| Object | recognized surname bearer |
—
|
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: recognized surname bearer | Statement: [José Pinzón, hasOnomasticNotability, recognized surname bearer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnomasticNotability Context triple: [José Pinzón, hasOnomasticNotability, recognized surname bearer]
-
A.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
B.
hasEponymNotability
Indicates that an entity is notable specifically for having something (such as a place, object, or concept) named after it.
-
C.
nameTypeNotability
Indicates that the type or category of a name is determined or influenced by the notability or prominence associated with it.
-
D.
hasOnomasticRelation
chosen
Indicates that there is a relationship between entities based on names, naming patterns, or shared onomastic (name-related) features.
-
E.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.