Triple
T34641333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Essex Regiment |
E889564
|
entity |
| Predicate | laterNameInSeries |
P16968
|
FINISHED |
| Object | Prince of Wales’s Own Volunteers |
—
|
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: Prince of Wales’s Own Volunteers | Statement: [South Essex Regiment, laterNameInSeries, Prince of Wales’s Own Volunteers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterNameInSeries Context triple: [South Essex Regiment, laterNameInSeries, Prince of Wales’s Own Volunteers]
-
A.
laterSeriesName
Indicates that one series is a subsequent or later-titled continuation or successor of another series.
-
B.
laterNamed
chosen
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
C.
laterAiredAs
Indicates that one media item was broadcast or released at a later time under a different title or format than the original.
-
D.
laterNameDevelopment
Indicates that an entity acquired or was given this name at a later stage in its development or history, rather than originally.
-
E.
laterAdaptationName
Indicates that the object is the name of a later adaptation derived from or based on the subject.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: May 1, 2026, 2:04 a.m.