Triple
T6935841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USAFAS |
E160550
|
entity |
| Predicate | militaryBranchDomain |
P74375
|
FINISHED |
| Object | artillery |
—
|
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: artillery | Statement: [USAFAS, militaryBranchDomain, artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchDomain Context triple: [USAFAS, militaryBranchDomain, artillery]
-
A.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
-
B.
militaryBranchComponentOf
Indicates that one military branch or unit is an organizational component or subordinate part of a larger military branch or force.
-
C.
militaryBranchAbbreviation
Indicates the standard shortened form or acronym used to represent a specific branch of a military organization.
-
D.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
E.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
- F. None of above. chosen
Provenance (4 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6e0c620f0819080e0ec49b36d4c30 |
completed | March 27, 2026, 7:55 p.m. |
Created at: March 27, 2026, 2:27 p.m.