Triple
T14014088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Household |
E337160
|
entity |
| Predicate | hasOfficialEvent |
P69091
|
FINISHED |
| Object | public appearances on the palace balcony |
—
|
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: public appearances on the palace balcony | Statement: [Imperial Household, hasOfficialEvent, public appearances on the palace balcony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialEvent Context triple: [Imperial Household, hasOfficialEvent, public appearances on the palace balcony]
-
A.
hasOfficialEvents
chosen
Indicates that an entity organizes, hosts, or is associated with formally recognized or sanctioned events.
-
B.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
C.
hasSportingEvent
Indicates that a sporting event is associated with, held at, or organized by a given entity.
-
D.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
E.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.