Triple
T37023452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Our Lady of Loreto |
E916282
|
entity |
| Predicate | hasPatronageLinkedTo |
P45407
|
FINISHED |
| Object | aviation |
—
|
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: aviation | Statement: [Feast of Our Lady of Loreto, hasPatronageLinkedTo, aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronageLinkedTo Context triple: [Feast of Our Lady of Loreto, hasPatronageLinkedTo, aviation]
-
A.
hasPatronageOver
chosen
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
B.
hasNotablePatron
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
-
C.
sharesPatronageWith
Indicates that two entities are supported, sponsored, or funded by the same patron or sponsoring party.
-
D.
hasPatronageContext
Indicates that one entity is involved with or characterized by a particular patronage relationship, setting, or circumstances.
-
E.
hasBeenLinkedTo
Indicates that an entity has been associated or connected with another entity, often suggesting a reported or inferred relationship between them.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 3, 2026, 4:14 p.m.