Triple
T8005332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Goa |
E186350
|
entity |
| Predicate | instagramHandle |
P3718
|
FINISHED |
| Object | @fcgoaofficial |
E701724
|
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: @fcgoaofficial | Statement: [FC Goa, instagramHandle, @fcgoaofficial]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: @fcgoaofficial Context triple: [FC Goa, instagramHandle, @fcgoaofficial]
-
A.
@FCGoaOfficial
chosen
@FCGoaOfficial is the official Twitter account of FC Goa, a professional football club competing in the Indian Super League.
-
B.
GFA
GFA is the ICAO airline designator used for Gulf Air, the national carrier of Bahrain.
-
C.
F.A.C.
F.A.C. is the standard legal abbreviation used to refer to the Florida Administrative Code, which contains the administrative rules and regulations of the state of Florida.
-
D.
FAFC
FAFC is the common abbreviation for Forfar Athletic Football Club, a Scottish professional football team based in the town of Forfar.
-
E.
GOC
GOC is the standardised set of spelling and writing rules used for modern Scottish Gaelic.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf72fc08190aa78b97c1ab92f90 |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc5697ac9081909fe7ca06d0c3ef38 |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:18 p.m.