Triple
T14394363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java bytecode |
E356918
|
entity |
| Predicate | programmingParadigmSupport |
P11868
|
FINISHED |
| Object | object-oriented programming |
—
|
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: object-oriented programming | Statement: [Java bytecode, programmingParadigmSupport, object-oriented programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingParadigmSupport Context triple: [Java bytecode, programmingParadigmSupport, object-oriented programming]
-
A.
supportedParadigm
chosen
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
-
B.
programmingParadigmWorkedOn
Indicates that an entity has worked on or been involved with a particular programming paradigm.
-
C.
languageParadigm
Indicates a relationship where a programming language follows, supports, or is categorized under a particular programming paradigm.
-
D.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
E.
hasProgrammingModel
Indicates that one entity defines, specifies, or is associated with the programming model used or supported by 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902d114881908a8f3c01b3c6d309 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.