Triple
T2547880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Cruising Voyage Round the World |
E57946
|
entity |
| Predicate | hasCastawayRescue |
P26805
|
FINISHED |
| Object | Alexander Selkirk on Juan Fernández Islands |
—
|
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: Alexander Selkirk on Juan Fernández Islands | Statement: [A Cruising Voyage Round the World, hasCastawayRescue, Alexander Selkirk on Juan Fernández Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastawayRescue Context triple: [A Cruising Voyage Round the World, hasCastawayRescue, Alexander Selkirk on Juan Fernández Islands]
-
A.
allegedRescueEvent
Indicates that an event is claimed or reported to be a rescue, but its occurrence or nature is not confirmed as factual.
-
B.
rescuedLocation
chosen
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
C.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
D.
crewEscapeCapability
Indicates that an entity has the capability or provision for its crew to escape safely in an emergency situation.
-
E.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e672948190bb7fe9b47535a172 |
completed | March 7, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.