Triple
T19592785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carillon Berlin |
E470276
|
entity |
| Predicate | hasLanguageOfPrograms |
P35567
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Carillon Berlin, hasLanguageOfPrograms, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfPrograms Context triple: [Carillon Berlin, hasLanguageOfPrograms, German]
-
A.
primaryLanguageOfPrograms
Indicates that a given language is the main programming language used to implement or develop the specified programs.
-
B.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
C.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
D.
hasLanguages
chosen
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
E.
hasTypicalPerformanceLanguage
Indicates that an entity is commonly or characteristically expressed, implemented, or described using a particular programming or specification language.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64057460c8190962e2e58f06b3985 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.