Triple
T33057383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trivium |
E845877
|
entity |
| Predicate | isPubliclyAnalyzed |
P176391
|
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, isPubliclyAnalyzed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPubliclyAnalyzed Context triple: [Trivium, isPubliclyAnalyzed, true]
-
A.
oftenAnalyzedIn
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
B.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
C.
dataPubliclyAvailable
Indicates that the referenced data is accessible to the general public without special permissions or restrictions.
-
D.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
E.
hasAnalyticUse
Indicates that something is used for analysis, examination, or systematic study of another thing or situation.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:25 a.m.