Triple
T1549776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlesex Regiment |
E33061
|
entity |
| Predicate | regimentalMotto |
P20052
|
FINISHED |
| Object | Firm |
—
|
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: Firm | Statement: [Middlesex Regiment, regimentalMotto, Firm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalMotto Context triple: [Middlesex Regiment, regimentalMotto, Firm]
-
A.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
B.
regimentalAssociation
Indicates a formal relationship in which an entity is affiliated with, belongs to, or is organized as part of a specific military regiment.
-
C.
regimentalMarch
Indicates a coordinated, rhythmic movement of a group in formation, typically following strict timing and alignment as in military drill.
-
D.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
E.
isMottoOf
chosen
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.