Triple
T8758963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XPF |
E208144
|
entity |
| Predicate | ISO4217Code |
P189
|
FINISHED |
| Object | XPF |
E208144
|
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: XPF | Statement: [XPF, ISO4217Code, XPF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XPF Context triple: [XPF, 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.
XPG
XPG is the IATA station code for Paris Gare du Nord, one of the main international railway hubs in Paris, France.
-
C.
XQUF
XQUF is the standardized extension to the XQuery language that adds capabilities for updating and modifying XML data.
-
D.
XAF
XAF is the currency code for the Central African CFA franc, a regional currency used by several Central African countries.
-
E.
W^X
W^X is a memory protection security mechanism that enforces pages to be either writable or executable, but not both, to mitigate exploits such as buffer overflows.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5df81c58819089af99306e103dbb |
completed | March 31, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf434232d08190bfee6f5ec1c0b5a6 |
completed | April 3, 2026, 4:34 a.m. |
Created at: March 30, 2026, 6:40 p.m.