Triple
T20545601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | franc Pacifique |
E504460
|
entity |
| Predicate | ISO4217Code |
P189
|
FINISHED |
| Object | XPF |
—
|
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: XPF | Statement: [franc Pacifique, ISO4217Code, XPF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XPF Context triple: [franc Pacifique, ISO4217Code, XPF]
-
A.
XPF
chosen
XPF is the CFP franc, a currency used in several French overseas collectivities in the Pacific, including French Polynesia.
-
B.
SXF
SXF is the standard abbreviation used for the Sioux Falls Skyforce, a professional basketball team in the NBA G League.
-
C.
SXF
SXF was the IATA airport code for Berlin Schönefeld Airport, the former secondary international airport serving Berlin, Germany.
-
D.
XPG
XPG is the IATA station code for Paris Gare du Nord, one of the main international railway hubs in Paris, France.
-
E.
XSF
XSF is the nonprofit organization that develops and maintains the open XMPP communication protocols used for instant messaging and real-time communication.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a29684648190969d8fc23743e288 |
completed | April 20, 2026, 10:03 p.m. |
Created at: April 16, 2026, 11:38 a.m.