Triple
T28669410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halloran House |
E725668
|
entity |
| Predicate | ownedByFictionalFamily |
P167373
|
FINISHED |
| Object | Halloran family |
—
|
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: Halloran family | Statement: [Halloran House, ownedByFictionalFamily, Halloran family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedByFictionalFamily Context triple: [Halloran House, ownedByFictionalFamily, Halloran family]
-
A.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
B.
ownedByFictionalCharacter
Indicates that something is possessed or owned by a fictional (not real-world) character.
-
C.
frequentedByFictionalFamily
Indicates that a place or establishment is regularly visited or commonly associated with a particular fictional family.
-
D.
ownsByFamily
Indicates that ownership of an entity is held collectively or primarily by a family rather than by an individual or non-family organization.
-
E.
creatorFamily
Indicates that one entity is a family member of the creator or originator of another entity.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 5:02 a.m.