Triple
T28619735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Interchange File Format |
E724350
|
entity |
| Predicate | topLevelChunkID |
P80513
|
FINISHED |
| Object | RIFF |
—
|
NE NERFINISHED |
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: RIFF | Statement: [Resource Interchange File Format, topLevelChunkID, RIFF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelChunkID Context triple: [Resource Interchange File Format, topLevelChunkID, RIFF]
-
A.
topLevelOf
Indicates that one entity is the highest or most overarching level within the structure or hierarchy of another entity.
-
B.
topLevel
chosen
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
-
C.
topLevelHierarchy
Indicates that an entity occupies the highest position or root level within a hierarchical structure, with no parent above it.
-
D.
topStructure
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
-
E.
topLevelStatus
Indicates the primary or overall status assigned at the highest level of an entity, process, or system.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.