Triple
T35016729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Adventure Time) |
E1010074
|
entity |
| Predicate | eventHistory |
P182011
|
FINISHED |
| Object | Mushroom War |
—
|
NE NERFINISHED |
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 | Statement: [Earth (Adventure Time), eventHistory, Mushroom War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventHistory Context triple: [Earth (Adventure Time), eventHistory, Mushroom War]
-
A.
operationalHistory
Indicates the record of how something has been used, functioned, or operated over time, including its past activities and events.
-
B.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
C.
recordsEventsVia
Indicates that one entity captures or logs events through the mechanism, system, or medium provided by another entity.
-
D.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
E.
platformHistory
Indicates a relationship where one entity records or represents the historical states, changes, or evolution of a platform over time.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.