Triple
T32974442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Problem of Thor Bridge |
E843614
|
entity |
| Predicate | fictionalEstateOwner |
P14482
|
FINISHED |
| Object | Neil Gibson |
—
|
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: Neil Gibson | Statement: [The Problem of Thor Bridge, fictionalEstateOwner, Neil Gibson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalEstateOwner Context triple: [The Problem of Thor Bridge, fictionalEstateOwner, Neil Gibson]
-
A.
hasFictionalProprietor
chosen
Indicates that something is owned, managed, or run by a fictional character or entity within a narrative context.
-
B.
houseOwnerInStory
Indicates that one entity is the owner of a house within the context or events of a particular story.
-
C.
estateRole
Indicates the specific function, capacity, or responsibility an entity holds in relation to an estate (such as owner, executor, or beneficiary).
-
D.
fictionalResidence
Indicates that one entity is the place where another entity lives or is based within a fictional or imaginary context.
-
E.
formerOwnerInFiction
Indicates that one entity is depicted in a fictional context as having previously owned another entity.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.