Triple
T28619737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Interchange File Format |
E724350
|
entity |
| Predicate | RIFXMeaning |
P164947
|
FINISHED |
| Object | big-endian RIFF variant |
—
|
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: big-endian RIFF variant | Statement: [Resource Interchange File Format, RIFXMeaning, big-endian RIFF variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RIFXMeaning Context triple: [Resource Interchange File Format, RIFXMeaning, big-endian RIFF variant]
-
A.
CISMeaning
Indicates that one concept, term, or symbol conveys, expresses, or stands for a particular meaning or interpretation in a given context.
-
B.
refrainMeaning
Indicates that one entity chooses not to perform an action or avoids engaging in a particular behavior or expression.
-
C.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
D.
objectMeaning
Indicates that one entity represents, expresses, or conveys the meaning or semantic content of another entity.
-
E.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:32 a.m.