Triple
T26366198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brampton Battalion |
E660339
|
entity |
| Predicate | operatedInBramptonTo |
P192476
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Brampton Battalion, operatedInBramptonTo, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInBramptonTo Context triple: [Brampton Battalion, operatedInBramptonTo, 2013]
-
A.
operatedNear
Indicates that one entity performed an operation or activity in close physical proximity to another entity.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
operatedFrom
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
E.
operatedStation
Indicates that one entity managed, ran, or was responsible for the operation of a particular station.
- F. None of above. chosen
Provenance (4 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: April 26, 2026, 10:55 p.m.