Triple
T9443375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PASCH school network support |
E227702
|
entity |
| Predicate | languagePromoted |
P72315
|
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: [PASCH school network support, languagePromoted, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languagePromoted Context triple: [PASCH school network support, languagePromoted, German]
-
A.
promotedLanguage
chosen
Indicates that one entity actively advocated for, advertised, or otherwise encouraged the use or adoption of a particular language.
-
B.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
C.
languageAdvocated
Indicates that an entity actively supports, promotes, or argues in favor of the use or adoption of a particular language.
-
D.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
E.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f3171248190b92ab990371e63f5 |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.