Triple
T35881973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infantry Assault Badge |
E1037533
|
entity |
| Predicate | bronzeClassEligibility |
P106510
|
FINISHED |
| Object | motorized infantry units |
—
|
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: motorized infantry units | Statement: [Infantry Assault Badge, bronzeClassEligibility, motorized infantry units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bronzeClassEligibility Context triple: [Infantry Assault Badge, bronzeClassEligibility, motorized infantry units]
-
A.
hasBronzeElement
Indicates that an entity includes or is associated with at least one element made of bronze.
-
B.
bronzeMedalist
Indicates that an entity finished third in a competition or event, earning the bronze medal.
-
C.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
D.
qualifyingFor
chosen
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
E.
bronzeMedalPolicy
Indicates a policy or rule governing the conditions under which a bronze medal is awarded or recognized.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.