Triple
T19134734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulysses |
E468406
|
entity |
| Predicate | associatedWithSeaVoyage |
P47434
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ulysses, associatedWithSeaVoyage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSeaVoyage Context triple: [Ulysses, associatedWithSeaVoyage, yes]
-
A.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
B.
associatedWithVoyage
Indicates a relationship where an entity is linked or connected to a specific voyage, journey, or trip.
-
C.
associatedWithSea
chosen
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
D.
shipCompanion
Indicates that one entity serves as a companion or partner accompanying another entity on a ship or sea voyage.
-
E.
seaVoyages
Indicates that one entity undertakes or is associated with journeys or travel by sea to or involving 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ec4c848190af450bf5bf8db5e7 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.