Triple
T31807314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 66th (Berkshire) Regiment of Foot |
E811907
|
entity |
| Predicate | redesignated |
P169127
|
FINISHED |
| Object | 66th Regiment of Foot |
—
|
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: 66th Regiment of Foot | Statement: [66th (Berkshire) Regiment of Foot, redesignated, 66th Regiment of Foot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redesignated Context triple: [66th (Berkshire) Regiment of Foot, redesignated, 66th Regiment of Foot]
-
A.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
-
B.
redesignatedVariant
chosen
Indicates that one entity has been assigned a new designation or identifier, replacing or superseding a previous variant.
-
C.
postwarRedesignationOf
Indicates the relationship in which an entity receives a new designation or identity as a result of postwar changes or reorganization.
-
D.
redesignationYear
Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
-
E.
subsequentDesignation
Indicates that one designation or status follows and replaces another in a sequence or timeline.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:43 p.m.