Triple
T18925773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Palace of Sintra |
E462966
|
entity |
| Predicate | significantPatron |
P44585
|
FINISHED |
| Object | King John I of Portugal |
—
|
NE NERFINISHED |
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: King John I of Portugal | Statement: [Royal Palace of Sintra, significantPatron, King John I of Portugal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantPatron Context triple: [Royal Palace of Sintra, significantPatron, King John I of Portugal]
-
A.
primaryPatron
chosen
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
B.
laterPatron
Indicates that one entity serves as a patron of another at a later time than some reference patronage relationship.
-
C.
typeOfPatronage
Indicates the specific kind or category of support, sponsorship, or backing that one entity provides to another.
-
D.
firstPerformancePatron
Indicates that the subject is a patron attending or supporting an entity (such as a show or artist) at its first performance.
-
E.
traditionalPatron
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b94e008190a0e9a70aaf6d18ed |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.