Triple
T30863684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volunteer Airmen |
E786131
|
entity |
| Predicate | mottoForBranch |
P170807
|
FINISHED |
| Object | air component of Tennessee National Guard |
—
|
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: air component of Tennessee National Guard | Statement: [Volunteer Airmen, mottoForBranch, air component of Tennessee National Guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoForBranch Context triple: [Volunteer Airmen, mottoForBranch, air component of Tennessee National Guard]
-
A.
mottoOfBranch
Indicates that a particular motto is officially associated with and represents a specific branch of an organization or institution.
-
B.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
C.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
D.
mottoOfOrganizationLocation
Indicates that a particular motto is associated with an organization specifically in a given location.
-
E.
mottoPresent
Indicates that an entity currently has an official motto associated with it.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:47 p.m.