Triple
T29137924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal 3 |
E738553
|
entity |
| Predicate | primaryIn-universeAuthor |
P173255
|
FINISHED |
| Object | Stanford 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: Stanford Pines | Statement: [Journal 3, primaryIn-universeAuthor, Stanford Pines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryIn-universeAuthor Context triple: [Journal 3, primaryIn-universeAuthor, Stanford Pines]
-
A.
otherIn-universeAuthors
chosen
Indicates that one entity is an author or creator of works within the fictional universe of another entity.
-
B.
fictionalUniverseAuthor
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
-
C.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
D.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
E.
in-universeStatus
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: April 28, 2026, 11:35 a.m.