Triple
T38567440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hernando Pinzón |
E928263
|
entity |
| Predicate | hasSurnameHistoricallyAssociatedWith |
P49952
|
FINISHED |
| Object | maritime history |
—
|
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: maritime history | Statement: [Hernando Pinzón, hasSurnameHistoricallyAssociatedWith, maritime history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameHistoricallyAssociatedWith Context triple: [Hernando Pinzón, hasSurnameHistoricallyAssociatedWith, maritime history]
-
A.
hasAncestralFamilyName
Indicates that an entity bears or is associated with a family name inherited from its ancestors.
-
B.
isHistoricalName
Indicates that a given name is a former or past designation historically used for an entity.
-
C.
isRecordedAsSurnameSinceCentury
Indicates that an entity has been documented or used as a surname starting from a specified century.
-
D.
associatedSurname
chosen
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
E.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.