Triple
T10930255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martín Alonso Pinzón |
E258183
|
entity |
| Predicate | helpedRecruit |
P28396
|
FINISHED |
| Object | crew for Columbus’s first voyage |
—
|
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: crew for Columbus’s first voyage | Statement: [Martín Alonso Pinzón, helpedRecruit, crew for Columbus’s first voyage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedRecruit Context triple: [Martín Alonso Pinzón, helpedRecruit, crew for Columbus’s first voyage]
-
A.
recruitsFor
chosen
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
B.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
C.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
D.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
E.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709f92088190a15ae3638d3b14fb |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.