Triple
T35053765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Theft Auto: San Andreas |
E1011401
|
entity |
| Predicate | cityInspiredBy |
P14480
|
FINISHED |
| Object | San Francisco |
—
|
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: San Francisco | Statement: [Grand Theft Auto: San Andreas, cityInspiredBy, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityInspiredBy Context triple: [Grand Theft Auto: San Andreas, cityInspiredBy, San Francisco]
-
A.
cityOfInfluence
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
B.
inspiredByPlace
chosen
Indicates that something (such as a work, idea, or creation) originates from or is significantly influenced by a particular location or environment.
-
C.
cityDepicted
Indicates that a work (such as an image, artwork, or document) visually or representationally depicts a particular city.
-
D.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
E.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
- F. None of above.
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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785cfbdc081908499d3d5341ee3c3 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.