Triple
T18350632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Priest (The Trial) |
E439657
|
entity |
| Predicate | relationshipToCourt |
P10690
|
FINISHED |
| Object | servant of the court |
—
|
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: servant of the court | Statement: [The Priest (The Trial), relationshipToCourt, servant of the court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCourt Context triple: [The Priest (The Trial), relationshipToCourt, servant of the court]
-
A.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
-
B.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
D.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
-
E.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f83b648190b473cf611851c666 |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.