Triple
T35064067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baits Houses |
E1011678
|
entity |
| Predicate | hasOccupancy |
P182070
|
FINISHED |
| Object | hundreds of students |
—
|
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: hundreds of students | Statement: [Baits Houses, hasOccupancy, hundreds of students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupancy Context triple: [Baits Houses, hasOccupancy, hundreds of students]
-
A.
hasOccupancyStatus
Indicates the current usage or availability state of something, such as whether it is occupied, vacant, or otherwise in use.
-
B.
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).
-
C.
chairOccupation
Indicates that an entity holds or occupies the position of chair (e.g., head or leader) within an organization, group, or committee.
-
D.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
E.
occupiedFrom
Indicates that an entity is in use or inhabited starting from a specified point in time.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.