Triple
T10079924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killeen, Texas |
E213872
|
entity |
| Predicate | servesMilitaryFamilies |
P91963
|
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: [Killeen, Texas, servesMilitaryFamilies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMilitaryFamilies Context triple: [Killeen, Texas, servesMilitaryFamilies, yes]
-
A.
militarySpouseOf
Indicates that one person is or was the legally recognized spouse of another person who is serving or has served in the military.
-
B.
supportedFamilyLifeOf
Indicates that one entity provided assistance or resources that helped sustain or improve the family life or family-related well-being of another entity.
-
C.
serviceDesignationFamily
Indicates that one service designation is part of the same family or grouping as another, reflecting a shared classification or closely related category.
-
D.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
E.
eligibleFamily
Indicates that one entity qualifies as a family member of another under specified eligibility rules or criteria.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd031ce748190bb71189afd331979 |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9 p.m.