Triple
T30877109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUOS |
E786507
|
entity |
| Predicate | userTerminalType |
P104198
|
FINISHED |
| Object | portable terminals |
—
|
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: portable terminals | Statement: [MUOS, userTerminalType, portable terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userTerminalType Context triple: [MUOS, userTerminalType, portable terminals]
-
A.
defaultTerminalEmulator
Indicates that one entity is configured or recognized as the standard or primary terminal emulator to be used by another entity or system.
-
B.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
C.
testedDeviceType
chosen
Indicates that one entity is the type or category of device on which another entity has been tested.
-
D.
usedPlatformType
Indicates that an entity makes use of or operates on a particular type or category of platform.
-
E.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d76a808190b24f5a4758a87832 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.