Triple
T8487614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Dordrecht |
E200868
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
FCD
FCD is the commonly used abbreviation for FC Dordrecht, a professional football club based in Dordrecht, Netherlands.
|
E737250
|
NE FINISHED |
How this triple was built (4 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: FCD | Statement: [FC Dordrecht, abbreviation, FCD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FCD Context triple: [FC Dordrecht, abbreviation, FCD]
-
A.
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.
-
B.
FFC
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
C.
FCF
FCF is the football federation that organizes and oversees football activities and competitions in Catalonia.
-
D.
FCH
FCH is the common abbreviation and nickname for 1. FC Heidenheim, a German professional football club.
-
E.
FC-DA
FC-DA is a member of the Fibre Channel standards family that defines specific protocols and specifications for high-speed storage area networking.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: FCD Triple: [FC Dordrecht, abbreviation, FCD]
Generated description
FCD is the commonly used abbreviation for FC Dordrecht, a professional football club based in Dordrecht, Netherlands.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: FCD Target entity description: FCD is the commonly used abbreviation for FC Dordrecht, a professional football club based in Dordrecht, Netherlands.
-
A.
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.
-
B.
FFC
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
C.
FCF
FCF is the football federation that organizes and oversees football activities and competitions in Catalonia.
-
D.
FCH
FCH is the common abbreviation and nickname for 1. FC Heidenheim, a German professional football club.
-
E.
FC-DA
FC-DA is a member of the Fibre Channel standards family that defines specific protocols and specifications for high-speed storage area networking.
- F. None of above. chosen
Provenance (5 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe556b5188190b1124effd7445803 |
completed | March 31, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce3a4e5be48190b5c598123ef75f8b |
completed | April 2, 2026, 9:43 a.m. |
| NEDg | Description generation | batch_69ce3d0323248190a076a209df98c96c |
completed | April 2, 2026, 9:55 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce3d7909f48190a46f58fca75d7740 |
completed | April 2, 2026, 9:57 a.m. |
Created at: March 30, 2026, 6:13 p.m.