Triple
T10186227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penge East railway station |
E236914
|
entity |
| Predicate | hasRailcode |
P27071
|
FINISHED |
| Object | PNE |
E847136
|
NE 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: PNE | Statement: [Penge East railway station, hasRailcode, PNE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PNE Context triple: [Penge East railway station, hasRailcode, PNE]
-
A.
PNE
PNE is a professional football club based in Preston, Lancashire, England, known for being one of the founding members of the English Football League.
-
B.
PNE
chosen
PNE is the National Rail station code for Penge East railway station in south London, England.
-
C.
PNE
PNE is the IATA airport code for Northeast Philadelphia Airport, a public airport serving the northeastern section of Philadelphia, Pennsylvania.
-
D.
PN
PN is the commonly used abbreviation for the National Parliament of East Timor, the country's unicameral legislative body.
-
E.
PN
PN is the station code for Penn–North station on the Baltimore Metro SubwayLink system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded790b488190b1ed4645554873cd |
completed | April 2, 2026, 4:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d32ad838b08190ab8c50a4108bba68 |
completed | April 6, 2026, 3:39 a.m. |
Created at: March 30, 2026, 9:12 p.m.