Triple
T6289450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina FC |
E140977
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | NCFC |
E140977
|
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: NCFC | Statement: [North Carolina FC, abbreviation, NCFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NCFC Context triple: [North Carolina FC, abbreviation, NCFC]
-
A.
North Carolina FC
chosen
North Carolina FC is a professional soccer club based in the Raleigh–Durham area that competes in the USL Championship.
-
B.
Forge FC
Forge FC is a professional soccer club based in Hamilton, Ontario, competing in the Canadian Premier League and known as one of its most successful and prominent teams.
-
C.
Civics FC
Civics FC is a Namibian football club based in Windhoek that competes in the country’s top-tier league.
-
D.
Valour FC
Valour FC is a professional soccer club based in Winnipeg, Manitoba, that competes in the Canadian Premier League.
-
E.
OCFC
OCFC is the commonly used abbreviation for Oxford City Football Club, an English football team based in Oxford.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0641a6ecc8190a63be0e3f0344a3f |
completed | March 22, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e418a9e4819083f446b05175e904 |
completed | March 27, 2026, 1:57 a.m. |
Created at: March 22, 2026, 4:26 p.m.