Triple
T10394425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Shades of Brown |
E244973
|
entity |
| Predicate | productionCompany |
P490
|
FINISHED |
| Object | SVT |
E251086
|
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: SVT | Statement: [Four Shades of Brown, productionCompany, SVT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SVT Context triple: [Four Shades of Brown, productionCompany, SVT]
-
A.
SVT
SVT (Special Vehicle Team) is Ford Motor Company's high-performance division responsible for developing enhanced, limited-production models like the Cobra R.
-
B.
SVT
chosen
SVT is Sweden's national public television broadcaster, known for providing news, entertainment, and cultural programming.
-
C.
SVT1
SVT1 is a major Swedish public television channel known for news, current affairs, and a broad range of general-interest programming.
-
D.
SVT2
SVT2 is a Swedish public television channel known for its focus on culture, current affairs, and minority-language programming.
-
E.
Svt
Svt is the station code for Strandvliet, a metro station in Amsterdam, Netherlands.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9b795fc8190aa50ce3c7360ff83 |
completed | April 7, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d795c8271c81908a6b67822050c06d |
completed | April 9, 2026, 12:04 p.m. |
Created at: April 6, 2026, 12:06 p.m.