Triple
T3380151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Governor's Mansion |
E71161
|
entity |
| Predicate | hasReceptionRoom |
P5521
|
FINISHED |
| Object | formal reception rooms |
—
|
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: formal reception rooms | Statement: [Alaska Governor's Mansion, hasReceptionRoom, formal reception rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReceptionRoom Context triple: [Alaska Governor's Mansion, hasReceptionRoom, formal reception rooms]
-
A.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
B.
hasRoom
chosen
Indicates that an entity possesses, contains, or is associated with a specific room.
-
C.
reception
Indicates the act of receiving or welcoming someone or something, often marking the initial acknowledgment or acceptance in an interaction or process.
-
D.
hasHomeLockerRoomFor
Indicates that one entity serves as the designated home locker room facility for another entity, such as a team or organization.
-
E.
hasConferenceSpace
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2ec38d88190be8c824daeca5ab6 |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.