Triple
T218777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester and Salford Yeomanry |
E4167
|
entity |
| Predicate | activeDuringCentury |
P1560
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Manchester and Salford Yeomanry, activeDuringCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeDuringCentury Context triple: [Manchester and Salford Yeomanry, activeDuringCentury, 19th century]
-
A.
activeInCentury
chosen
Indicates that an entity was active, influential, or operational during a specified century.
-
B.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
C.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
D.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
E.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5199d8819096736c11077adec3 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.