Triple
T3901270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ServusTV (historical) |
E90493
|
entity |
| Predicate | programmingStyle |
P52759
|
FINISHED |
| Object | mix of sports and culture |
—
|
LITERAL 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: mix of sports and culture | Statement: [ServusTV (historical), programmingStyle, mix of sports and culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingStyle Context triple: [ServusTV (historical), programmingStyle, mix of sports and culture]
-
A.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
B.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
C.
protocolStyle
Indicates the manner or format in which a protocol or communication procedure is structured or expressed.
-
D.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
E.
programmingReputation
Indicates the level of recognition or esteem an entity has earned for its programming-related skills, contributions, or performance.
- F. None of above. chosen
Provenance (4 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef1aada308190821a3dfa6af170b3 |
completed | March 9, 2026, 4:13 p.m. |
Created at: March 9, 2026, 3:21 p.m.