Triple
T33057358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trivium |
E845877
|
entity |
| Predicate | eSTREAMProfile |
P175760
|
FINISHED |
| Object | Profile 2 |
—
|
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: Profile 2 | Statement: [Trivium, eSTREAMProfile, Profile 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eSTREAMProfile Context triple: [Trivium, eSTREAMProfile, Profile 2]
-
A.
enrollmentProfile
Indicates that an entity is associated with a specific enrollment configuration or set of enrollment settings.
-
B.
systemProfileStandard
Indicates that a system’s configuration or characteristics conform to a defined standard profile.
-
C.
stagingProfile
Indicates a temporary or preparatory configuration or environment used before final deployment or release.
-
D.
isStreamer
Indicates that the subject regularly broadcasts live content over an online streaming platform.
-
E.
definesProfileType
Indicates that an entity specifies or assigns the particular profile type associated with another entity.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.