Triple
T17939871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guntakal division |
E448557
|
entity |
| Predicate | railwayZoneCode |
P58492
|
FINISHED |
| Object | SCR |
—
|
NE NERFINISHED |
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: SCR | Statement: [Guntakal division, railwayZoneCode, SCR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SCR Context triple: [Guntakal division, railwayZoneCode, SCR]
-
A.
SCR
SCR at St Chad’s College refers to the Senior Common Room, the community and social/academic body of the college’s senior members, including fellows and staff.
-
B.
SCR
SCR is the commonly used abbreviation for the Sheffield City Region, a metropolitan area and combined authority in South Yorkshire, England, centered on the city of Sheffield.
-
C.
SCR
chosen
SCR refers to the South Central Railway zone of Indian Railways, which administers and operates train services across parts of southern and central India.
-
D.
SCR
SCR is the FAA location identifier for Siler City Municipal Airport, a public-use airport serving Siler City in North Carolina.
-
E.
SCR
SCR is the abbreviation for the Scottish Central Railway, a historic railway company that operated key routes in central Scotland during the 19th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 10:21 a.m.