Triple
T4570559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Gallery (Rideau Hall) |
E123018
|
entity |
| Predicate | primaryUseContext |
P10000
|
FINISHED |
| Object | vice-regal events |
—
|
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: vice-regal events | Statement: [Long Gallery (Rideau Hall), primaryUseContext, vice-regal events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseContext Context triple: [Long Gallery (Rideau Hall), primaryUseContext, vice-regal events]
-
A.
primaryFunctionContext
Indicates the main situational or operational context in which a function, role, or process is primarily intended to be used or performed.
-
B.
primaryUseInFeed
Indicates that something is the main or most common way an item is used or presented within a feed.
-
C.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
D.
usedPrimarilyIn
chosen
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
E.
primaryWorkContext
Indicates the main environment, setting, or domain in which an entity typically performs its work or primary activities.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c3eba48190af1fce6e1ca16943 |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.