Triple
T29137925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal 3 |
E738553
|
entity |
| Predicate | otherIn-universeAuthors |
P173255
|
FINISHED |
| Object | Dipper Pines |
—
|
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: Dipper Pines | Statement: [Journal 3, otherIn-universeAuthors, Dipper Pines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherIn-universeAuthors Context triple: [Journal 3, otherIn-universeAuthors, Dipper Pines]
-
A.
fictionalUniverseAuthor
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
-
B.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
C.
workAuthoredInUniverse
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
-
D.
sharesFictionalUniverseWith
Indicates that two entities are set within the same fictional universe or continuity, such that their stories coexist in a shared narrative world.
-
E.
authorshipInFiction
Indicates that one entity is the creator or writer of a fictional work in which another entity appears or is represented.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 28, 2026, 11:35 a.m.