Triple
T10820099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco |
E255343
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | Frisco |
E636123
|
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: Frisco | Statement: [San Francisco, hasNickname, Frisco]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frisco Context triple: [San Francisco, hasNickname, Frisco]
-
A.
Frisco
chosen
Frisco is the popular nickname for the historic St. Louis–San Francisco Railway, a major American railroad that operated across the Midwest and South.
-
B.
Frisco, Texas
Frisco, Texas is a rapidly growing suburban city in the Dallas–Fort Worth metropolitan area known for its sports venues, retail centers, and family-friendly communities.
-
C.
Grand Prairie
Grand Prairie is a mid-sized suburban city in the Dallas–Fort Worth metropolitan area known for its family attractions, parks, and growing residential communities.
-
D.
San Antonio
San Antonio is a major Chilean port city known for its significant role in the country’s maritime trade and fishing industries.
-
E.
San Antonio
San Antonio is a metro station on Line 7 of the Mexico City Metro system, serving passengers in the southwestern part of Mexico City.
- 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_69e3e6d27d8c8190b2c8ee9c54cf7fd1 |
completed | April 18, 2026, 8:17 p.m. |
Created at: April 8, 2026, 9:18 p.m.