Triple
T17058441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rai stones |
E413889
|
entity |
| Predicate | transportRisk |
P125687
|
FINISHED |
| Object | dangerous sea voyages |
—
|
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: dangerous sea voyages | Statement: [Rai stones, transportRisk, dangerous sea voyages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportRisk Context triple: [Rai stones, transportRisk, dangerous sea voyages]
-
A.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
B.
transportProject
Indicates a project whose primary purpose is to plan, build, improve, or manage transportation systems, services, or infrastructure.
-
C.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
D.
transportationImpact
Indicates how one entity’s transportation-related activities or characteristics affect another entity or the surrounding environment.
-
E.
transportAdvisory
Indicates that guidance, warnings, or recommendations are being issued regarding transportation conditions, operations, or usage.
- F. None of above. chosen
Provenance (4 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7b553c81908ec70ba0d0988710 |
completed | April 18, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.