Triple
T4416598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Literate Programming |
E94988
|
entity |
| Predicate | languageAgnostic |
P34874
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Literate Programming, languageAgnostic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageAgnostic Context triple: [Literate Programming, languageAgnostic, true]
-
A.
languageNeutral
Indicates that the relationship or action is independent of any specific natural language, applying uniformly across different linguistic contexts.
-
B.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
C.
isProgrammingLanguageIndependent
chosen
Indicates that something (such as a concept, algorithm, or interface) does not depend on any specific programming language and can be applied or used across different languages.
-
D.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
E.
code
Indicates that an entity writes, develops, or produces computer software or source code.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551afb448190a2ce2000193808ac |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.