Triple
T26400694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharagpur Junction |
E663687
|
entity |
| Predicate | hasVeryLongPlatform |
P164836
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kharagpur Junction, hasVeryLongPlatform, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVeryLongPlatform Context triple: [Kharagpur Junction, hasVeryLongPlatform, true]
-
A.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure of another entity.
-
B.
hasSidePlatformCount
Indicates the number of side platforms associated with an entity, such as a station or stop.
-
C.
hasDeepPlatform
Indicates that one entity possesses or provides a platform characterized by significant depth, capability, or extensiveness in supporting another entity’s activities or functions.
-
D.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
-
E.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 26, 2026, 11:31 p.m.