Triple
T3303465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Date Line |
E69390
|
entity |
| Predicate | deviatesToAvoid |
P12935
|
FINISHED |
| Object | landmasses |
—
|
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: landmasses | Statement: [International Date Line, deviatesToAvoid, landmasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviatesToAvoid Context triple: [International Date Line, deviatesToAvoid, landmasses]
-
A.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
B.
avoidsRoute
chosen
Indicates that an entity deliberately does not use or travel along a particular route.
-
C.
triedToAvoid
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
-
D.
hasNavigationHazard
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
-
E.
hasNavigationHazardRelevance
Indicates that something is relevant to, affected by, or poses a potential hazard to navigation.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.