Triple
T4029226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Untempered Schism |
E83665
|
entity |
| Predicate | viewingDescribedAs |
P21336
|
FINISHED |
| Object | gazing into the Time Vortex |
—
|
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: gazing into the Time Vortex | Statement: [Untempered Schism, viewingDescribedAs, gazing into the Time Vortex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingDescribedAs Context triple: [Untempered Schism, viewingDescribedAs, gazing into the Time Vortex]
-
A.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
B.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
-
C.
visionOf
Indicates that one entity is a visual representation, image, or depiction of another entity.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
viewedBySomeAs
chosen
Indicates that at least one observer or group perceives or interprets an entity in a particular way or role.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaf066b08190afbb4a18ddc8d67e |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.