Triple
T37263746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Logistics |
E924323
|
entity |
| Predicate | mottoOfUnitType |
P504
|
FINISHED |
| Object | reserve component unit |
—
|
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: reserve component unit | Statement: [Combat Logistics, mottoOfUnitType, reserve component unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoOfUnitType Context triple: [Combat Logistics, mottoOfUnitType, reserve component unit]
-
A.
mottoOfRegiment
Indicates that a particular phrase or motto is officially associated with and represents a specific military regiment.
-
B.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
C.
mottoType
chosen
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
D.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
E.
parentRegimentMotto
Indicates that one regiment’s motto is derived from, associated with, or officially linked to the motto of its parent regiment.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.