Triple
T13496306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Are Chaos |
E320769
|
entity |
| Predicate | intendedListeningOrder |
P37518
|
FINISHED |
| Object | continuous narrative |
—
|
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: continuous narrative | Statement: [We Are Chaos, intendedListeningOrder, continuous narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedListeningOrder Context triple: [We Are Chaos, intendedListeningOrder, continuous narrative]
-
A.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
-
C.
orderOfInteraction
Indicates the sequence or ranking in which interactions occur relative to one another.
-
D.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
-
E.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4e9ca4819083116890a65389f9 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.