Triple
T275596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Judicial Court |
E5241
|
entity |
| Predicate | includesRole |
P1393
|
FINISHED |
| Object | Chief Justice |
—
|
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: Chief Justice | Statement: [Supreme Judicial Court, includesRole, Chief Justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRole Context triple: [Supreme Judicial Court, includesRole, Chief Justice]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
C.
requiresRole
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
-
D.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
E.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd1cdf881909c2c9b77b7f88684 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7480e881909399beccfc7ffb81 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.