Triple
T14699654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Shepherd |
E345258
|
entity |
| Predicate | hasLivingCondition |
P94666
|
FINISHED |
| Object | long-term street homelessness |
—
|
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: long-term street homelessness | Statement: [Miss Shepherd, hasLivingCondition, long-term street homelessness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivingCondition Context triple: [Miss Shepherd, hasLivingCondition, long-term street homelessness]
-
A.
hasLivingEnvironment
Indicates that an entity exists or resides within a particular living environment or habitat.
-
B.
isLiving
Indicates that an entity is currently alive or possesses life.
-
C.
livedWithConditionFor
chosen
Indicates that an entity has experienced and coexisted with a particular condition for a specified duration or period of time.
-
D.
hasHousingArrangement
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
E.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb604f88081908a677175045496d0 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.