Triple
T16088818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Drawing Room |
E390304
|
entity |
| Predicate | roomFunction |
P57668
|
FINISHED |
| Object | reception |
—
|
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: reception | Statement: [Crimson Drawing Room, roomFunction, reception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roomFunction Context triple: [Crimson Drawing Room, roomFunction, reception]
-
A.
roomFunctionContext
chosen
Indicates the contextual role or purpose a room serves within a particular situation, activity, or usage scenario.
-
B.
houseCommonRoom
Indicates that a house or dwelling includes or is associated with a shared common room space used collectively by its occupants.
-
C.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
-
D.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
E.
controlRoomFeature
Indicates that a feature, element, or characteristic is part of, present in, or associated with a control room.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.