Triple
T17894743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FPC |
E447403
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | FPC |
—
|
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: FPC | Statement: [FPC, abbreviation, FPC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FPC Context triple: [FPC, abbreviation, FPC]
-
A.
FPC
FPC is the abbreviated name of the Federal Passenger Company, a major Russian railway operator specializing in long-distance and suburban passenger transport.
-
B.
FPC
FPC is the common abbreviation for the Farah Palmer Cup, New Zealand’s premier women’s provincial rugby union competition.
-
C.
F-PC
F-PC is a notable implementation of the Forth programming language designed for use on personal computers.
-
D.
FFC
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
E.
FFC
FFC is the common abbreviation for Fluminense Football Club, a traditional Brazilian sports club best known for its professional football team based in Rio de Janeiro.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7ccf808190b4c1fd477043bcc8 |
completed | April 19, 2026, 9:16 a.m. |
Created at: April 10, 2026, 10:19 a.m.