Triple
T9998350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCSS Prometheus |
E197260
|
entity |
| Predicate | hasOnboard |
P36407
|
FINISHED |
| Object | med-pod |
—
|
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: med-pod | Statement: [USCSS Prometheus, hasOnboard, med-pod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboard Context triple: [USCSS Prometheus, hasOnboard, med-pod]
-
A.
hasOnboardFeature
chosen
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
B.
hasOnboardButton
Indicates that one entity is equipped with or includes a button installed on or within it.
-
C.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
D.
hadOnboardService
Indicates that an onboard service was provided or available during a particular trip, journey, or transport event.
-
E.
onboarding
Indicates the process by which an entity is introduced, integrated, and given the necessary resources or information to begin participating in or using another entity (such as a system, organization, or service).
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8c78448190a5332f4ff8a7b3dd |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.