Triple
T15208633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Power |
E363453
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | PAFC |
E1145439
|
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: PAFC | Statement: [The Power, abbreviation, PAFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PAFC Context triple: [The Power, abbreviation, PAFC]
-
A.
PAFC
chosen
PAFC is an abbreviation that commonly stands for "power" in technical or engineering contexts.
-
B.
PAFC
PAFC is the commonly used abbreviation for Plymouth Argyle Football Club, a professional English football team based in Plymouth, Devon.
-
C.
FAFC
FAFC is the common abbreviation for Forfar Athletic Football Club, a Scottish professional football team based in the town of Forfar.
-
D.
PaF
PaF is a Portuguese centre-right political coalition formed by the Social Democratic Party and the CDS – People's Party to contest national elections.
-
E.
PAC
PAC is the commonly used abbreviation for the Pacific Division, a grouping of teams in various North American professional sports leagues.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b8e2788190bd1831762e4181ae |
completed | April 15, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fee5e9e2d8819086ca62ca6037dd1c |
completed | May 9, 2026, 7:44 a.m. |
Created at: April 10, 2026, 3:11 a.m.