Triple
T31653391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patryk |
E807793
|
entity |
| Predicate | sharesPatronSaintWith |
P142740
|
FINISHED |
| Object | Patrick |
—
|
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: Patrick | Statement: [Patryk, sharesPatronSaintWith, Patrick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPatronSaintWith Context triple: [Patryk, sharesPatronSaintWith, Patrick]
-
A.
saintPatronageAssociatedWith
Indicates that a patronage relationship exists, where a saint is recognized as a special protector or advocate for a particular person, group, place, activity, or cause.
-
B.
coPatronSaint
chosen
Indicates that two or more saints share the role of patronage over the same place, group, or cause.
-
C.
hasPatronSaint
Indicates that one entity serves as the patron saint associated with, protecting, or representing another entity.
-
D.
patronSaintCelebrated
Indicates that a particular patron saint is honored or commemorated, typically through religious or cultural observances, by a specific community, place, or group.
-
E.
nationalPatronSaint
Indicates that one entity is recognized as the official patron saint of a particular nation.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: April 30, 2026, 10:54 p.m.