Triple
T11570972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minionese |
E274383
|
entity |
| Predicate | isFullyDevelopedLanguage |
P100380
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Minionese, isFullyDevelopedLanguage, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFullyDevelopedLanguage Context triple: [Minionese, isFullyDevelopedLanguage, false]
-
A.
isInflectedLanguage
Indicates that a language uses systematic changes in word form (inflections) to express grammatical categories such as tense, case, number, or gender.
-
B.
developedForLanguage
Indicates that something (such as a tool, system, or resource) was specifically created or adapted to be used with a particular language.
-
C.
supportsDevelopmentLanguage
Indicates that one entity provides compatibility with, tools for, or the ability to use a particular programming or development language.
-
D.
isWorldLanguage
Indicates that a language is widely used across multiple countries or regions and serves as a common means of communication beyond its original native community.
-
E.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd6913881908becf188c0a7a275 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.