Triple
T35557835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remember You |
E1027548
|
entity |
| Predicate | chronologicallyLinkedTo |
P94975
|
FINISHED |
| Object | Mushroom War backstory |
—
|
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: Mushroom War backstory | Statement: [Remember You, chronologicallyLinkedTo, Mushroom War backstory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyLinkedTo Context triple: [Remember You, chronologicallyLinkedTo, Mushroom War backstory]
-
A.
chronologicallyInvolvedIn
Indicates that an entity participates in or is associated with an event, process, or activity during a specific time period in a chronological sequence.
-
B.
chronologicallyBelongsTo
Indicates that one temporal entity or event falls within, or is properly associated with, a specific time period or chronological grouping.
-
C.
chronologicallyOrdered
chosen
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
chronologicallyAmong
Indicates that one event or time point occurs within the temporal range defined by two other events or time points, preserving their chronological order.
-
E.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:04 p.m.