Triple
T32582984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Smith (Mr. & Mrs. Smith) |
E832839
|
entity |
| Predicate | homeLifeSetting |
P55894
|
FINISHED |
| Object | suburban house |
—
|
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: suburban house | Statement: [John Smith (Mr. & Mrs. Smith), homeLifeSetting, suburban house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeLifeSetting Context triple: [John Smith (Mr. & Mrs. Smith), homeLifeSetting, suburban house]
-
A.
homeLifeDescription
chosen
Indicates a description of an entity’s domestic or everyday living situation and conditions.
-
B.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
-
C.
homeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
D.
homeSystem
Indicates that one entity is the primary or originating system, base, or environment associated with another entity.
-
E.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66b3190819099566cd27a999b77 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.