Triple
T29690666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurorae |
E751201
|
entity |
| Predicate | themeFormat |
P167603
|
FINISHED |
| Object | Aurorae theme |
—
|
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: Aurorae theme | Statement: [Aurorae, themeFormat, Aurorae theme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeFormat Context triple: [Aurorae, themeFormat, Aurorae theme]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
C.
themeKey
Indicates that one entity serves as the primary subject, topic, or thematic focus associated with another entity.
-
D.
themeRepresentation
Indicates that one entity serves as a representation, depiction, or expression of the thematic content associated with another entity.
-
E.
themeTreatment
Indicates that a treatment is applied to, affects, or is directed toward a particular theme or subject.
- F. None of above. chosen
Provenance (4 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6729454bc8190b00ca425f7336a01 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:16 p.m.