Triple
T1996266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinta |
E43365
|
entity |
| Predicate | roleInVoyage |
P24306
|
FINISHED |
| Object | fastest of Columbus's three ships |
—
|
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: fastest of Columbus's three ships | Statement: [Pinta, roleInVoyage, fastest of Columbus's three ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInVoyage Context triple: [Pinta, roleInVoyage, fastest of Columbus's three ships]
-
A.
roleInExpedition
chosen
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
B.
aboardShip
Indicates that one entity is physically on or inside a ship, typically as a passenger, crew member, or cargo.
-
C.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
D.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
E.
voyageType
Indicates the specific category or nature of a journey or trip that an entity undertakes.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.