Triple
T10259407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Case of the S.S. "Lotus" |
E240555
|
entity |
| Predicate | incidentLocation |
P26084
|
FINISHED |
| Object | high seas |
—
|
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: high seas | Statement: [The Case of the S.S. "Lotus", incidentLocation, high seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentLocation Context triple: [The Case of the S.S. "Lotus", incidentLocation, high seas]
-
A.
siteOfAccident
chosen
Indicates the location where an accident occurred.
-
B.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
C.
involvedLocation
Indicates that an event, action, or relationship takes place in, or is significantly associated with, a particular location.
-
D.
incidentCharacterization
Indicates how an incident is classified or characterized in terms of its nature, attributes, or type.
-
E.
encounterLocation
Indicates the place or setting where two or more entities meet, interact, or come into contact.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:32 a.m.