Triple
T6497639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FACh |
E148797
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | FACh |
E148797
|
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: FACh | Statement: [FACh, acronym, FACh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FACh Context triple: [FACh, acronym, FACh]
-
A.
FACh
chosen
FACh is the acronym for the Chilean Air Force, the aerial warfare branch of Chile's armed forces.
-
B.
FCH
FCH is the common abbreviation and nickname for 1. FC Heidenheim, a German professional football club.
-
C.
FAC
FAC is a renowned multidisciplinary cultural center and contemporary art space in Havana, Cuba, known for its fusion of visual arts, music, performance, and nightlife.
-
D.
FAC
FAC is the commonly used abbreviation for the Foreign Affairs Council, the European Union body where member states’ foreign ministers coordinate and decide on EU external policy.
-
E.
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.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c68ace80108190804a835bc646b2b2 |
completed | March 27, 2026, 1:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cb0ff914819080b1721ccbc56571 |
completed | March 27, 2026, 6:23 p.m. |
Created at: March 27, 2026, 1:41 p.m.