Triple
T29612509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Battalion |
E754764
|
entity |
| Predicate | uniformAssociation |
P118854
|
FINISHED |
| Object | Royal Life Guards dress uniforms |
—
|
NE NERFINISHED |
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: Royal Life Guards dress uniforms | Statement: [3rd Battalion, uniformAssociation, Royal Life Guards dress uniforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformAssociation Context triple: [3rd Battalion, uniformAssociation, Royal Life Guards dress uniforms]
-
A.
primaryUniformAssociation
Indicates that one entity is designated as the main or primary uniform associated with another entity.
-
B.
uniformAffiliation
chosen
Indicates that an entity is associated with, authorized to wear, or represented by a particular uniform or standardized attire.
-
C.
localAssociation
Indicates a relationship where entities are connected or interact within the same local area, context, or community.
-
D.
antAssociation
Indicates a relationship in which one entity is associated or interacts in a specific, notable way with ants.
-
E.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66debb6388190a53898d0d12c7ad5 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:29 p.m.