Triple
T36710545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasi |
E906783
|
entity |
| Predicate | governingBodyAssociatedWith |
P24141
|
FINISHED |
| Object | Sanhedrin |
E385203
|
NE 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: Sanhedrin | Statement: [Nasi, governingBodyAssociatedWith, Sanhedrin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyAssociatedWith Context triple: [Nasi, governingBodyAssociatedWith, Sanhedrin]
-
A.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
B.
governingBody2
chosen
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
C.
governingBodyId
Indicates the entity that serves as the official governing body responsible for overseeing or managing another entity.
-
D.
governingBodyOrSupport
Indicates that one entity serves as the governing authority for, or provides official support to, another entity.
-
E.
governingBodyRepresents
Indicates that a governing body acts on behalf of, and makes decisions representing the interests or authority of, another entity.
- F. None of above.
Provenance (4 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a382ec49c8190a7dcaac1209b7910 |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:12 p.m.