Triple
T15515002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 37 (information in cases of deaths, guardianship, wrecks, and air accidents) |
E368812
|
entity |
| Predicate | requiresNotificationOf |
P41194
|
FINISHED |
| Object | shipwrecks involving vessels flying the flag of the sending State |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: shipwrecks involving vessels flying the flag of the sending State | Statement: [Article 37 (information in cases of deaths, guardianship, wrecks, and air accidents), requiresNotificationOf, shipwrecks involving vessels flying the flag of the sending State]
Provenance (2 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
Created at: April 10, 2026, 4:02 a.m.