Triple
T24928499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIF |
E618925
|
entity |
| Predicate | containerStructure |
P125792
|
FINISHED |
| Object | sequence of blocks |
—
|
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: sequence of blocks | Statement: [GIF, containerStructure, sequence of blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containerStructure Context triple: [GIF, containerStructure, sequence of blocks]
-
A.
containmentStructure
chosen
Indicates that one entity serves as a physical or logical container or enclosing structure for another entity.
-
B.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
C.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
D.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
E.
verticalStructure
Indicates a relationship where one entity is a structure that extends predominantly in the vertical direction relative to another reference or context.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 18, 2026, 5:29 a.m.