Triple
T14710400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullen family |
E345531
|
entity |
| Predicate | primaryResidenceType |
P542
|
FINISHED |
| Object | secluded house in the forest |
—
|
LITERAL FINISHED |
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: secluded house in the forest | Statement: [Cullen family, primaryResidenceType, secluded house in the forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResidenceType Context triple: [Cullen family, primaryResidenceType, secluded house in the forest]
-
A.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
B.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
C.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
-
D.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
E.
residenceStatus
Indicates the type or condition of an entity’s living arrangement or place of residence in relation to a specified location.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb9814e0c8190984ac30d276499cc |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.