Triple
T35162733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmon House |
E1015311
|
entity |
| Predicate | residedInByCharacter |
P116758
|
FINISHED |
| Object | Ben Harmon |
—
|
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: Ben Harmon | Statement: [Harmon House, residedInByCharacter, Ben Harmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residedInByCharacter Context triple: [Harmon House, residedInByCharacter, Ben Harmon]
-
A.
residentInFiction
Indicates that one entity is a fictional character or element that resides or exists within the fictional setting, world, or universe represented by another entity.
-
B.
believedToResideIn
Indicates that one entity is thought or assumed to live or be located in a particular place or region, without confirming this as a verified fact.
-
C.
workLocationOfFictionalCharacter
Indicates the place or organization where a fictional character is depicted as working within their narrative context.
-
D.
residedOn
chosen
Indicates that an entity lived or had its primary dwelling at a specific location during a certain period.
-
E.
cityOfFictionalResidence
Indicates that a fictional character or entity resides in, or is associated with living in, a particular city within a narrative or fictional context.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.