Triple
T1848371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. FC Nürnberg |
E41334
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | FCN |
E206219
|
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: FCN | Statement: [1. FC Nürnberg, hasAbbreviation, FCN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FCN Context triple: [1. FC Nürnberg, hasAbbreviation, FCN]
-
A.
FCN
chosen
FCN is the common abbreviation for 1. FC Nürnberg, a German football club based in Nuremberg.
-
B.
Fon
Fon is a major Gbe language of West Africa, primarily spoken by the Fon people in Benin and neighboring countries.
-
C.
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.
-
D.
FFC
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
E.
JFC
JFC is the commonly used abbreviation for the United Kingdom's Joint Forces Command, a major military command responsible for overseeing joint capabilities across the armed services.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb05412a08190855ea453d1264ea3 |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf48e3048190a79824fd92e0079f |
completed | March 8, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:33 p.m.