Triple
T17462305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese royal court |
E425182
|
entity |
| Predicate | heldCeremonies |
P20938
|
FINISHED |
| Object | royal audiences |
—
|
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: royal audiences | Statement: [Portuguese royal court, heldCeremonies, royal audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldCeremonies Context triple: [Portuguese royal court, heldCeremonies, royal audiences]
-
A.
ceremonyHeld
chosen
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
B.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
-
C.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
D.
ceremonyIncludes
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
E.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a4c36c81909c7c4b1b0d976921 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.