Triple
T218801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester and Salford Yeomanry |
E4167
|
entity |
| Predicate | unitType |
P6008
|
FINISHED |
| Object | local militia-style cavalry |
—
|
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: local militia-style cavalry | Statement: [Manchester and Salford Yeomanry, unitType, local militia-style cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitType Context triple: [Manchester and Salford Yeomanry, unitType, local militia-style cavalry]
-
A.
typeOfUnit
chosen
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
D.
hostsUnit
Indicates that one entity serves as the location or container in which another unit is situated, operates, or is organized.
-
E.
chamberType
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
- 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.