Triple
T29139815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meg bedroom |
E738592
|
entity |
| Predicate | occupantStatus |
P26411
|
FINISHED |
| Object | single-occupancy bedroom |
—
|
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: single-occupancy bedroom | Statement: [Meg bedroom, occupantStatus, single-occupancy bedroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupantStatus Context triple: [Meg bedroom, occupantStatus, single-occupancy bedroom]
-
A.
hasOccupantStatus
Indicates that an entity holds a particular role, status, or condition as an occupant of another entity (such as a place, vehicle, or property).
-
B.
hasOccupancyStatus
chosen
Indicates the current usage or availability state of something, such as whether it is occupied, vacant, or otherwise in use.
-
C.
fieldOfOccupant
Indicates the specific professional or academic field in which an occupant is engaged or associated.
-
D.
politicalStatusOfOccupant
Indicates the political role, affiliation, or status held by the occupant of a given position, place, or office.
-
E.
tenantOccupation
Indicates that an entity occupies or uses a property or premises as a tenant under a rental or lease arrangement.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 11:36 a.m.