Triple
T20676881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FESPIC Games |
E508181
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | FESPIC |
—
|
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: FESPIC | Statement: [FESPIC Games, acronym, FESPIC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FESPIC Context triple: [FESPIC Games, acronym, FESPIC]
-
A.
FESPIC Games
chosen
FESPIC Games were a major multi-sport event for athletes with disabilities from the Far East and South Pacific regions, serving as a key precursor to the Asian Para Games.
-
B.
FSP
FSP is the station code used to identify Schweizer Platz station in the Frankfurt public transport network.
-
C.
FSP
FSP is the abbreviation for the Feuerschutzpolizei, the fire protection police units that operated in Nazi Germany.
-
D.
FSP
FSP is a maximum-security correctional facility in Florida known for housing some of the state’s most dangerous inmates and operating the state’s execution chamber.
-
E.
FSP
FSP is the commonly used abbreviation for Folsom State Prison, a historic maximum-security penitentiary in California.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea24f288190928f828e5f567257 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 11:44 a.m.