Triple
T31815316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAMP/T |
E812116
|
entity |
| Predicate | networkCentricCapability |
P28147
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SAMP/T, networkCentricCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkCentricCapability Context triple: [SAMP/T, networkCentricCapability, yes]
-
A.
networkCenter
Indicates that an entity functions as the central or primary hub within a network, coordinating or connecting other nodes.
-
B.
operationalCapability
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
-
C.
routingCapability
Indicates the ability of an entity to determine and direct the path that data, messages, or items should take through a network or system.
-
D.
networkFocus
Indicates a relationship where attention, resources, or activity are primarily directed toward a particular network or set of network connections.
-
E.
networkCharacteristic
chosen
Indicates a relationship where a specific property or feature is attributed to a network or networking context.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 11:44 p.m.