Triple
T30878639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dutch House |
E786547
|
entity |
| Predicate | houseFunctionInStory |
P175379
|
FINISHED |
| Object | symbol of family legacy |
—
|
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: symbol of family legacy | Statement: [The Dutch House, houseFunctionInStory, symbol of family legacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseFunctionInStory Context triple: [The Dutch House, houseFunctionInStory, symbol of family legacy]
-
A.
houseOwnerInStory
Indicates that one entity is the owner of a house within the context or events of a particular story.
-
B.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
C.
homeLocationInStory
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
D.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
-
E.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 29, 2026, 8:48 p.m.