Triple
T17975917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christophoros |
E449469
|
entity |
| Predicate | hasPatronageAssociation |
P2830
|
FINISHED |
| Object | travelers |
—
|
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: travelers | Statement: [Christophoros, hasPatronageAssociation, travelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronageAssociation Context triple: [Christophoros, hasPatronageAssociation, travelers]
-
A.
hasPatronageOver
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.
hasPatronalSignificanceIn
Indicates that something holds special protective, dedicatory, or patron-related importance within a particular context, such as a place, group, or institution.
-
E.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fee86c8190a9a220b008e78e10 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.