Triple

T10866115
Position Surface form Disambiguated ID Type / Status
Subject PNE E256533 entity
Predicate shortName P43 FINISHED
Object PNE E256533 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: [PNE, shortName, PNE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PNE
Context triple: [PNE, shortName, PNE]
  • A. PNE chosen
    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
    PNE is the IATA airport code for Northeast Philadelphia Airport, a public airport serving the northeastern section of Philadelphia, Pennsylvania.
  • C. PNE
    PNE is the National Rail station code for Penge East railway station in south London, England.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7516cebe881909ed358a7641f6a12 completed April 9, 2026, 7:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69dff7d7b32081909dd5f8ae3fe293be completed April 15, 2026, 8:40 p.m.
Created at: April 8, 2026, 9:20 p.m.