Triple
T33057384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trivium |
E845877
|
entity |
| Predicate | hasSoftwareImplementations |
P70127
|
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: [Trivium, hasSoftwareImplementations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoftwareImplementations Context triple: [Trivium, hasSoftwareImplementations, true]
-
A.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
-
B.
hasOpenSourceImplementationsIn
Indicates that something has one or more open-source implementations available in the specified environment, platform, or language.
-
C.
areImplementedBy
chosen
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by another entity.
-
D.
usesSoftwareModel
Indicates that one entity employs or relies on a particular software model to perform its functions or tasks.
-
E.
implementedFor
Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:25 a.m.