Triple
T27941713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julia Bernhardt |
E700766
|
entity |
| Predicate | appearsInFictionalUniverseOf |
P79039
|
FINISHED |
| Object | Pete Murphy |
—
|
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: Pete Murphy | Statement: [Julia Bernhardt, appearsInFictionalUniverseOf, Pete Murphy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInFictionalUniverseOf Context triple: [Julia Bernhardt, appearsInFictionalUniverseOf, Pete Murphy]
-
A.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
B.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
hasFictionalUniverseType
Indicates that an entity is associated with, or belongs to, a particular type or category of fictional universe.
-
D.
activeInFictionalUniverse
chosen
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
-
E.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 7:18 p.m.