Triple
T93777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Space Force |
E1884
|
entity |
| Predicate | serviceBranchNumber |
P2099
|
FINISHED |
| Object | sixth branch of the U.S. Armed Forces |
—
|
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: sixth branch of the U.S. Armed Forces | Statement: [United States Space Force, serviceBranchNumber, sixth branch of the U.S. Armed Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchNumber Context triple: [United States Space Force, serviceBranchNumber, sixth branch of the U.S. Armed Forces]
-
A.
serviceBranch
chosen
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
C.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
D.
branchCount
Indicates the number of branches associated with a given entity or structure.
-
E.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.