Triple
T28592238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacDowell |
E723681
|
entity |
| Predicate | hasResidencyModel |
P62756
|
FINISHED |
| Object | communal meals with solitary work time |
—
|
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: communal meals with solitary work time | Statement: [MacDowell, hasResidencyModel, communal meals with solitary work time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidencyModel Context triple: [MacDowell, hasResidencyModel, communal meals with solitary work time]
-
A.
hasResidenceFeature
chosen
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
B.
residencyStatus
Indicates the legal or official residential classification of an entity within a particular jurisdiction or context.
-
C.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
D.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
E.
hasCanonicalResidence
Indicates that an entity has an officially recognized primary place of residence or domicile.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: April 28, 2026, 4:20 a.m.