Triple
T4600162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenBSD |
E100302
|
entity |
| Predicate | supportsFileSystem |
P203
|
FINISHED |
| Object | FFS2 |
E198692
|
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: FFS2 | Statement: [OpenBSD, supportsFileSystem, FFS2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FFS2 Context triple: [OpenBSD, supportsFileSystem, FFS2]
-
A.
FFS
FFS is the commonly used abbreviation for the Swiss Federal Railways, the national railway company of Switzerland.
-
B.
FFSv2
chosen
FFSv2 is the second-generation Fast File System used by NetBSD and other BSD-derived operating systems, offering improved performance, larger file and filesystem size support, and enhanced reliability over the original FFS.
-
C.
FFC
FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
-
D.
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.
-
E.
FFM
FFM is an abbreviation commonly used for the Montreal World Film Festival, an international film festival held annually in Montreal, Canada.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5971f448819090f6e76c7d3ffc2d |
completed | March 20, 2026, 2:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be0349e89c8190a94e72bdc1e4e59f |
completed | March 21, 2026, 2:32 a.m. |
Created at: March 20, 2026, 1:11 p.m.