Triple
T7016011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolkata Metro |
E162700
|
entity |
| Predicate | peakRole |
P75264
|
FINISHED |
| Object | major commuter transport for Kolkata |
—
|
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: major commuter transport for Kolkata | Statement: [Kolkata Metro, peakRole, major commuter transport for Kolkata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakRole Context triple: [Kolkata Metro, peakRole, major commuter transport for Kolkata]
-
A.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
B.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
C.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
E.
peakReign
Indicates the period or point in time when an entity’s power, influence, or dominance was at its highest.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e5eb904481909a900e2ba9df710b |
completed | March 27, 2026, 8:17 p.m. |
Created at: March 27, 2026, 2:34 p.m.