Triple
T7264875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Edward Alleyn |
E159745
|
entity |
| Predicate | significantPatronOf |
P44585
|
FINISHED |
| Object | education |
—
|
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: education | Statement: [Sir Edward Alleyn, significantPatronOf, education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantPatronOf Context triple: [Sir Edward Alleyn, significantPatronOf, education]
-
A.
typeOfPatronage
Indicates the specific kind or category of support, sponsorship, or backing that one entity provides to another.
-
B.
laterPatron
Indicates that one entity serves as a patron of another at a later time than some reference patronage relationship.
-
C.
usedAsPatronOf
Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
-
D.
primaryPatron
chosen
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
E.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.