Triple
T38218840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USM Auriga |
E1010753
|
entity |
| Predicate | onboardAI |
P21784
|
FINISHED |
| Object | ship computer system |
—
|
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: ship computer system | Statement: [USM Auriga, onboardAI, ship computer system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardAI Context triple: [USM Auriga, onboardAI, ship computer system]
-
A.
onBoard
Indicates that one entity is physically located on or within a vehicle, vessel, or platform operated or used by another entity.
-
B.
onboardPlatform
Indicates that an entity is being added, integrated, or enrolled onto a particular platform so it can start operating or participating there.
-
C.
onboardProcessing
Indicates that processing or computation is performed directly on or within the platform, device, or system where the data originates, rather than being offloaded elsewhere.
-
D.
hasOnboardSystems
chosen
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
coPilotOf
Indicates that one entity serves as the co-pilot assisting and supporting another entity in operating or navigating a vehicle or craft.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.