Triple
T3418247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gradle |
E72061
|
entity |
| Predicate | buildScriptLanguage |
P11936
|
FINISHED |
| Object | Groovy DSL |
—
|
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: Groovy DSL | Statement: [Gradle, buildScriptLanguage, Groovy DSL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildScriptLanguage Context triple: [Gradle, buildScriptLanguage, Groovy DSL]
-
A.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
-
B.
scriptInventor
Indicates that one entity is the creator or originator of a particular writing system or script used by another entity.
-
C.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
D.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
E.
scriptSystem
chosen
Indicates that one entity is the scripting or programming system used to control, configure, or automate the behavior of another entity.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92df1e48190bbf22a47e44579f1 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.