Triple
T20861018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Par railway station |
E513616
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | PAR |
—
|
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: PAR | Statement: [Par railway station, stationCode, PAR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PAR Context triple: [Par railway station, stationCode, PAR]
-
A.
PAR
PAR is the IATA city code representing the collective airport system serving Paris, France, including major airports such as Charles de Gaulle and Orly.
-
B.
PAR
PAR is the standard abbreviation used for the Parramatta Eels, a professional rugby league club based in Sydney, Australia.
-
C.
PAR
PAR is a keyword in the Occam programming language used to specify that a group of processes should execute concurrently.
-
D.
Par
Par is a shortened variant of the surname "Parr," commonly used as a family name in various cultures.
-
E.
Par
chosen
Par is a small coastal village in Cornwall, England, known for its beach, harbour, and proximity to the town of Fowey.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3aba3d0819093431f38f0095a71 |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 12:44 p.m.