Triple
T29667511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army Soldier Support Institute |
E750568
|
entity |
| Predicate | componentServed |
P84790
|
FINISHED |
| Object | Active Component |
—
|
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: Active Component | Statement: [U.S. Army Soldier Support Institute, componentServed, Active Component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentServed Context triple: [U.S. Army Soldier Support Institute, componentServed, Active Component]
-
A.
servesPartOf
chosen
Indicates that one entity functions as a service or provider that operates within, or as a component of, another larger system or context.
-
B.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 7:02 p.m.