Triple
T25239734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Theatre Carré |
E632431
|
entity |
| Predicate | hasLanguageOfProgramming |
P169209
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Royal Theatre Carré, hasLanguageOfProgramming, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfProgramming Context triple: [Royal Theatre Carré, hasLanguageOfProgramming, Dutch]
-
A.
hasProgrammingFrom
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
-
B.
hasProgrammingDomain
Indicates that an entity is associated with or specializes in a particular programming domain or area of software development.
-
C.
languageOfPrimaryProgramming
Indicates the programming language that is primarily used to implement or develop a given entity.
-
D.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
E.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 21, 2026, 1:07 p.m.