Triple
T33857886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room 309 |
E867835
|
entity |
| Predicate | hasRoomNumber |
P181937
|
FINISHED |
| Object | 309 |
—
|
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: 309 | Statement: [Room 309, hasRoomNumber, 309]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoomNumber Context triple: [Room 309, hasRoomNumber, 309]
-
A.
hasRoom
Indicates that an entity possesses, contains, or is associated with a specific room.
-
B.
chamberNumber
chosen
Indicates the specific numbered chamber or room associated with an entity within a larger building or structure.
-
C.
hasUnitNumber
Indicates that an entity is associated with a specific unit identifier or number within a larger building, complex, or organizational structure.
-
D.
hasMapRoom
Indicates that an entity includes or provides access to a dedicated room or space used for displaying or working with maps.
-
E.
hasGateNumber
Indicates that an entity (such as a flight or departure) is associated with a specific gate number.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 1, 2026, 1:47 a.m.