Triple
T10842549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tboli |
E255924
|
entity |
| Predicate | T’nalakDesignsInspiredBy |
P62284
|
FINISHED |
| Object | dreams |
—
|
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: dreams | Statement: [Tboli, T’nalakDesignsInspiredBy, dreams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: T’nalakDesignsInspiredBy Context triple: [Tboli, T’nalakDesignsInspiredBy, dreams]
-
A.
designsBy
Indicates that one entity is the creator or designer responsible for the conception or design of another entity.
-
B.
sharesDesignTraditionWith
Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
-
C.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
D.
inspiredWorks
Indicates that one work served as a source of inspiration or creative influence for the creation or development of another work.
-
E.
inspiredWorksOf
chosen
Indicates that one entity served as the source of inspiration or creative influence for the works produced by another entity.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750ce40108190895c477553195fe4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.