Triple

T12268970
Position Surface form Disambiguated ID Type / Status
Subject IEN 41 E292422 entity
Predicate title P38 FINISHED
Object IEN 41 E292422 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: IEN 41 | Statement: [IEN 41, title, IEN 41]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: IEN 41
Context triple: [IEN 41, title, IEN 41]
  • A. IEN 41 chosen
    IEN 41 is an early Internet Experiment Note documenting research and design considerations in the formative stages of the ARPANET/Internet protocols.
  • B. ME 114
    ME 114 is a state highway in Maine that runs through parts of Cumberland County, connecting several communities and serving as a regional commuter and local access route.
  • C. ME 111
    ME 111 is a state highway in Maine that serves as a key east–west route connecting several communities in the southern part of the state.
  • D. ME 115
    ME 115 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
  • E. ME 121
    ME 121 is a state highway in Maine that serves as a regional connector route through several communities in the western part of the state.
  • 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_69d6ab6856488190b5d31178d5015f8e completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cdea6e881908e13f8259bad6ddc completed April 10, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69f61e6799088190a5644267733ca2e5 completed May 2, 2026, 3:55 p.m.
Created at: April 8, 2026, 9:52 p.m.