Triple
T12898944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Software Freedom Law Center |
E308566
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SFLC |
E308566
|
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: SFLC | Statement: [Software Freedom Law Center, abbreviation, SFLC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SFLC Context triple: [Software Freedom Law Center, abbreviation, SFLC]
-
A.
SFLC
chosen
SFLC is a legal organization that provides pro bono counsel and advocacy to protect and advance free and open-source software.
-
B.
SFL
SFL is the commonly used abbreviation for the Scottish Football League, the former governing body for professional league football in Scotland.
-
C.
SFL
SFL is the commonly used abbreviation for the Swiss Super League, the top tier of professional football in Switzerland.
-
D.
LFLC
LFLC is the ICAO airport code for Clermont-Ferrand Auvergne Airport in central France.
-
E.
SLSF
SLSF was the reporting mark used by the St. Louis–San Francisco Railway, commonly known as the Frisco, a major Midwestern and Southern U.S. railroad.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717f3fc48190b61c8f6f36cd0725 |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a56189b081909ed838addcb6d265 |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:40 p.m.