Triple
T16649876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SF Studios |
E404573
|
entity |
| Predicate | hasBrand |
P1500
|
FINISHED |
| Object | SF Anytime |
E1226260
|
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 Anytime | Statement: [SF Studios, hasBrand, SF Anytime]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SF Anytime Context triple: [SF Studios, hasBrand, SF Anytime]
-
A.
SF Anytime
chosen
SF Anytime is a Nordic video-on-demand service offering digital rentals and purchases of films and TV series.
-
B.
AT&SF
AT&SF is the common abbreviation for the Atchison, Topeka and Santa Fe Railway, one of the major historic railroad systems in the United States.
-
C.
SM By the Bay
SM By the Bay is a popular seaside leisure and entertainment complex along Manila Bay known for its restaurants, rides, and sunset views.
-
D.
SFJ
SFJ is the ICAO airline designator for StarFlyer, a Japanese low-cost carrier based at Kitakyushu Airport.
-
E.
SF
SF is the standard two-letter postal abbreviation used to represent the city of San Francisco, California.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad85ec881909dc6a434a363dab1 |
completed | April 18, 2026, 12:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a2f1da48190a1a01dbe25f8f0e9 |
completed | May 10, 2026, 1:37 p.m. |
Created at: April 10, 2026, 5:18 a.m.