Triple
T15043827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR.N1 |
E379170
|
entity |
| Predicate | canTravelOver |
P74272
|
FINISHED |
| Object | water |
—
|
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: water | Statement: [SR.N1, canTravelOver, water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTravelOver Context triple: [SR.N1, canTravelOver, water]
-
A.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
B.
travelCapability
chosen
Indicates the ability or capacity of an entity to move or be transported from one location to another.
-
C.
travelFreedom
Indicates the degree to which an entity is allowed or able to move or travel freely across locations or jurisdictions without restriction.
-
D.
hasAirTravelLink
Indicates that there is a direct or established air travel connection (such as flights or air routes) between the related entities.
-
E.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82f73208190bb55fa6b20074e27 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.