Triple
T5577564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainbow (Interlude) |
E146357
|
entity |
| Predicate | hasWorkLength |
P32671
|
FINISHED |
| Object | brief |
—
|
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: brief | Statement: [Rainbow (Interlude), hasWorkLength, brief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkLength Context triple: [Rainbow (Interlude), hasWorkLength, brief]
-
A.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
B.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
C.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
D.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
E.
workLength
chosen
Indicates the duration or length of time associated with a particular work or task.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0206ae4808190971d89243db94475 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.