Triple
T7138090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Valley of Adventure |
E166360
|
entity |
| Predicate | hasRecurringProtagonists |
P75055
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Valley of Adventure, hasRecurringProtagonists, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringProtagonists Context triple: [The Valley of Adventure, hasRecurringProtagonists, true]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
protagonistCount
Indicates the number of primary protagonists involved in a given narrative or work.
-
C.
reprisePerformersInStory
Indicates that certain performers reappear in the same roles or capacities within a subsequent part or version of the story.
-
D.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
E.
hasFlashbackStorylines
Indicates that the narrative includes scenes or sequences set in earlier time periods that reveal past events related to the main storyline.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6939b788190929e92ff481f2ee4 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:45 p.m.