Triple
T38345675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shogun |
E1041531
|
entity |
| Predicate | religiousRelationship |
P201877
|
FINISHED |
| Object | patron of Buddhist temples |
—
|
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: patron of Buddhist temples | Statement: [shogun, religiousRelationship, patron of Buddhist temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousRelationship Context triple: [shogun, religiousRelationship, patron of Buddhist temples]
-
A.
religiousRelation
chosen
Indicates a relationship between entities based on shared or differing religious affiliation, belief, practice, or institutional connection.
-
B.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
C.
familyRelationshipStatus
Indicates the type and state of a familial relationship that exists between two entities.
-
D.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
E.
sexualRelationshipTo
Indicates that one entity has engaged in a sexual relationship or sexual activity with another entity.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: May 3, 2026, 4:30 p.m.