Triple
T10951339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LORAN |
E258732
|
entity |
| Predicate | userEquipment |
P9919
|
FINISHED |
| Object | LORAN receiver |
—
|
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: LORAN receiver | Statement: [LORAN, userEquipment, LORAN receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userEquipment Context triple: [LORAN, userEquipment, LORAN receiver]
-
A.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
B.
usesDevice
chosen
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
featuresDevice
Indicates that one entity includes, incorporates, or provides the other entity as a device within it or as part of its functionality.
-
D.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
E.
device
Indicates that one entity is a device used, controlled, or referenced by another entity in the relationship.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fc156c8190826e124c13ce7242 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.