Triple
T23046406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco |
E573887
|
entity |
| Predicate | regionCode |
P208
|
FINISHED |
| Object | SF |
—
|
NE NERFINISHED |
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: SF | Statement: [San Francisco, regionCode, SF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SF Context triple: [San Francisco, regionCode, SF]
-
A.
SF
chosen
SF is the standard two-letter postal abbreviation used to represent the city of San Francisco, California.
-
B.
SF
SF is the IATA airline designator assigned to Tassili Airlines, an Algerian carrier.
-
C.
SF
SF is the abbreviated name commonly used for SF Studios, a major Swedish film production and distribution company.
-
D.
SF
SF is a Norwegian football club based in Sandefjord, known for competing in the country’s professional league system.
-
E.
SV
SV is the two-letter ISO 3166-1 alpha-2 country code assigned to El Salvador.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185192754819093a87d23371e7bbc |
completed | April 29, 2026, 4:12 a.m. |
Created at: April 17, 2026, 3:54 p.m.