Triple
T7155571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacGregor House (W61) |
E166802
|
entity |
| Predicate | hasLivingStyle |
P3562
|
FINISHED |
| Object | suite-style living |
—
|
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: suite-style living | Statement: [MacGregor House (W61), hasLivingStyle, suite-style living]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivingStyle Context triple: [MacGregor House (W61), hasLivingStyle, suite-style living]
-
A.
supportsLifestyle
Indicates that one entity provides the resources, conditions, or assistance necessary for another entity to maintain a particular way of living.
-
B.
lifestyle
chosen
Indicates that an entity’s way of living or habitual behaviors are associated with, influence, or characterize another entity or outcome.
-
C.
isLiving
Indicates that an entity is currently alive or possesses life.
-
D.
hasWorkStyle
Indicates the type or manner in which an entity typically performs work or carries out tasks.
-
E.
usesHouseStyle
Indicates that one entity follows or applies the specific house style (a defined set of stylistic or formatting conventions) associated with another entity.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80c747c8190a017a2b1c3e78a3f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.