Triple
T13268274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 49th (Hertfordshire) Regiment of Foot |
E315980
|
entity |
| Predicate | typeOfRegiment |
P56207
|
FINISHED |
| Object | numbered regiment of foot |
—
|
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: numbered regiment of foot | Statement: [49th (Hertfordshire) Regiment of Foot, typeOfRegiment, numbered regiment of foot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRegiment Context triple: [49th (Hertfordshire) Regiment of Foot, typeOfRegiment, numbered regiment of foot]
-
A.
regimentalCategory
chosen
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
B.
regimentalFamily
Indicates a familial or close-kin relationship that exists within, or is defined by, a shared regimental or military unit affiliation.
-
C.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
typeOfCadetForce
Indicates the specific category or kind of cadet force to which an entity belongs.
-
E.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.