Triple
T29193629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detective Nick Yemana |
E740062
|
entity |
| Predicate | houseSpecialty |
P169672
|
FINISHED |
| Object | office coffee |
—
|
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: office coffee | Statement: [Detective Nick Yemana, houseSpecialty, office coffee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseSpecialty Context triple: [Detective Nick Yemana, houseSpecialty, office coffee]
-
A.
houseTraitAssociation
Indicates an associative relationship between a house and a particular trait or characteristic attributed to it.
-
B.
houseEmphasis
Indicates that a particular house or housing-related element is given special focus, priority, or prominence relative to others.
-
C.
houseElement
Indicates that one entity is a structural or functional component of a house associated with another entity.
-
D.
servesHouse
Indicates that an entity provides service, support, or functions on behalf of a particular house or household.
-
E.
houseUse
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 28, 2026, 12:03 p.m.