Triple
T250791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSV Limiting Factor |
E5141
|
entity |
| Predicate | navigatesUsing |
P8588
|
FINISHED |
| Object | sonar systems |
—
|
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: sonar systems | Statement: [DSV Limiting Factor, navigatesUsing, sonar systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigatesUsing Context triple: [DSV Limiting Factor, navigatesUsing, sonar systems]
-
A.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
C.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
D.
reopenedForNavigation
Indicates that something previously closed to traffic or passage has been opened again for navigational use.
-
E.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.