Triple
T10820100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco |
E255343
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | SF |
E1413
|
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: SF | Statement: [San Francisco, hasNickname, SF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SF Context triple: [San Francisco, hasNickname, SF]
-
A.
SF
chosen
SF is the standard two-letter postal abbreviation used to represent the city of San Francisco, California.
-
B.
SV
SV is the two-letter ISO 3166-1 alpha-2 country code assigned to El Salvador.
-
C.
SV
SV is the commonly used abbreviation for the Faculty of Social Sciences at the University of Oslo, encompassing disciplines such as sociology, political science, economics, and related fields.
-
D.
SV
SV is a Norwegian democratic socialist and environmentalist political party known for its left-wing stance on social justice, welfare, and climate policy.
-
E.
SV
SV is the official abbreviation for the Slovenian Armed Forces, the military organization responsible for defending the Republic of Slovenia.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73449eee88190afa52c4e6ef96baa |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de8569178481909474e939a3e4c217 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.