Triple
T25156191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army heraldry |
E626319
|
entity |
| Predicate | designPrinciplesInclude |
P162863
|
FINISHED |
| Object | unit lineage |
—
|
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: unit lineage | Statement: [U.S. Army heraldry, designPrinciplesInclude, unit lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPrinciplesInclude Context triple: [U.S. Army heraldry, designPrinciplesInclude, unit lineage]
-
A.
designPhilosophy
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
-
B.
designCriteria
Indicates the standards, requirements, or constraints that guide how something should be planned, structured, or created.
-
C.
componentPrinciple
Indicates that one entity serves as a fundamental component or underlying principle that structurally or conceptually supports or governs another entity.
-
D.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
E.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 18, 2026, 6:30 a.m.