Triple
T18178736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barking Abbey |
E435227
|
entity |
| Predicate | hadRoyalPatronage |
P48229
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Barking Abbey, hadRoyalPatronage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRoyalPatronage Context triple: [Barking Abbey, hadRoyalPatronage, true]
-
A.
hasRoyalPatronageSince
Indicates that an entity has been under the official support or sponsorship of a royal person or institution starting from a specified point in time.
-
B.
grantedRoyalPatronageBy
chosen
Indicates that an individual, group, or institution has officially received support, endorsement, or sponsorship from a member of a royal family.
-
C.
historicalPatron
Indicates that one entity served as a patron or sponsor of another in a historical context, providing support, protection, or resources.
-
D.
historicalDynastyPatron
Indicates that a historical dynasty acted as a patron or sponsor, providing support or endorsement to another entity.
-
E.
discoveredUnderPatronageOf
Indicates that something was discovered with the support, sponsorship, or protection of a particular patron or benefactor.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df5b68f081908aac8210270f1499 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.