Triple
T30887933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 32nd Regiment of Foot |
E786817
|
entity |
| Predicate | regimentalNumberAdopted |
P113166
|
FINISHED |
| Object | 1751 |
—
|
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: 1751 | Statement: [32nd Regiment of Foot, regimentalNumberAdopted, 1751]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalNumberAdopted Context triple: [32nd Regiment of Foot, regimentalNumberAdopted, 1751]
-
A.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
B.
hasRegimentNumber
chosen
Indicates that an entity (such as a military unit) is assigned a specific regiment number as its identifying designation.
-
C.
hasRegimentalIdentity
Indicates that an entity possesses or is associated with a specific regimental identity, such as belonging to or being characterized by a particular regiment.
-
D.
hasBattalionNumber
Indicates that an entity (such as a military unit) is associated with a specific battalion number identifier.
-
E.
parentRegimentDesignation
Indicates that one military regiment is designated as the parent or higher-level regiment to which another regiment belongs or from which it is derived.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692071d00819083948e17acfe2644 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.