Triple
T29408345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entropy |
E745830
|
entity |
| Predicate | rigoIs |
P166751
|
FINISHED |
| Object | graphical user interface |
—
|
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: graphical user interface | Statement: [Entropy, rigoIs, graphical user interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rigoIs Context triple: [Entropy, rigoIs, graphical user interface]
-
A.
hasRIO
Indicates that an entity is associated with, or possesses, a specific Region of Interest (RIO) in a given context.
-
B.
seRigePor
Indicates that one entity is governed, regulated, or guided by the rules, principles, or criteria established by another entity or system.
-
C.
Bravio delle Botti
Indicates a relationship involving participation in, association with, or occurrence during the Bravio delle Botti barrel-racing event.
-
D.
rom
Indicates a romantic relationship or romantic involvement between the related entities.
-
E.
RIC
Indicates a relationship in which one entity is responsible for insuring or providing insurance coverage to another entity or asset.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a35eeb48190872f62f2e455ffee |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:55 p.m.