Triple
T3244944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java Card |
E68046
|
entity |
| Predicate | supportsLanguageSubset |
P19951
|
FINISHED |
| Object | Java Card language subset |
—
|
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: Java Card language subset | Statement: [Java Card, supportsLanguageSubset, Java Card language subset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLanguageSubset Context triple: [Java Card, supportsLanguageSubset, Java Card language subset]
-
A.
hasSubLanguage
chosen
Indicates that one language is a subset, variant, or specialized form of another language.
-
B.
hasSubstrateLanguage
Indicates a relationship where one language serves as the underlying substrate that has influenced or shaped another language.
-
C.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
D.
includesMajorLanguageFamily
Indicates that one entity encompasses, contains, or is associated with a major language family as part of its scope or classification.
-
E.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf1982448190b3d60c9e4471421f |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.