Triple
T9798230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumbleweeds (resident writers and travelers) |
E237769
|
entity |
| Predicate | hasHousingForm |
P67334
|
FINISHED |
| Object | improvised beds in the bookshop |
—
|
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: improvised beds in the bookshop | Statement: [Tumbleweeds (resident writers and travelers), hasHousingForm, improvised beds in the bookshop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHousingForm Context triple: [Tumbleweeds (resident writers and travelers), hasHousingForm, improvised beds in the bookshop]
-
A.
housingForm
chosen
Indicates the type or structure of housing associated with an entity (e.g., apartment, single-family home, dormitory).
-
B.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
C.
hasHousingPolicy
Indicates that an entity possesses, adopts, or is governed by a specific housing-related policy or set of rules.
-
D.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
E.
hasHousingUnits
Indicates that an entity possesses or contains a specified number or set of housing units.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda627cc2c81909ccc2e26751f5e85 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.