Triple
T13795385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8 Diagrams |
E331501
|
entity |
| Predicate | recordLabel |
P1500
|
FINISHED |
| Object | SRC Records |
E561938
|
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: SRC Records | Statement: [8 Diagrams, recordLabel, SRC Records]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SRC Records Context triple: [8 Diagrams, recordLabel, SRC Records]
-
A.
SRC Records
chosen
SRC Records is an American hip hop-focused record label known for signing prominent rap artists such as Remy Ma.
-
B.
S Records
S Records is a music record label associated with releasing work by the artist Thankful.
-
C.
SAR Records
SAR Records was an independent record label from the early 1960s closely associated with soul and gospel music and the career of Sam Cooke.
-
D.
SRC
SRC is a Canadian French-language television network owned by the Canadian Broadcasting Corporation, serving as its primary public broadcasting service in French.
-
E.
SRC
SRC is the station code for Santragachi Junction, a major railway station serving the Howrah–Kolkata area in West Bengal, India.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0259b0e4819081c11ced694384fb |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b08508688190b7e8c33e6b65e25d |
completed | May 3, 2026, 8:31 p.m. |
Created at: April 9, 2026, 10:11 p.m.