Triple
T207260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontius Pilate |
E4635
|
entity |
| Predicate | legalRole |
P5610
|
FINISHED |
| Object | Roman judicial authority in Judea |
—
|
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: Roman judicial authority in Judea | Statement: [Pontius Pilate, legalRole, Roman judicial authority in Judea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRole Context triple: [Pontius Pilate, legalRole, Roman judicial authority in Judea]
-
A.
legalProfessionRole
chosen
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
B.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
C.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
D.
legalPersonality
Indicates that an entity possesses recognized legal status, enabling it to hold rights, bear obligations, and act as a subject under the law.
-
E.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.