Triple
T10259454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.S. Lotus |
E240556
|
entity |
| Predicate | collisionLocation |
P90022
|
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: [S.S. Lotus, collisionLocation, high seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionLocation Context triple: [S.S. Lotus, collisionLocation, high seas]
-
A.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
B.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
C.
trapLocation
Indicates the specific place or area where a trap is set, located, or expected to be found.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
collisionZone
chosen
Indicates a spatial region within which objects are considered to be in contact or impact with one another, typically used to detect or handle collisions.
- 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.