Triple
T32270421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC special constables (patrol) |
E824400
|
entity |
| Predicate | identifiableBy |
P177371
|
FINISHED |
| Object | TTC special constable crests and markings |
—
|
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: TTC special constable crests and markings | Statement: [TTC special constables (patrol), identifiableBy, TTC special constable crests and markings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiableBy Context triple: [TTC special constables (patrol), identifiableBy, TTC special constable crests and markings]
-
A.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
B.
identifiability
Indicates that an entity or set of entities can be uniquely distinguished or determined based on the available information or observations.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
identified
Indicates that one entity has recognized, named, or established the identity of another entity.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 12:42 a.m.