Triple
T24500488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaestiones |
E617918
|
entity |
| Predicate | juristRankOfAuthor |
P140026
|
FINISHED |
| Object | eminent jurist |
—
|
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: eminent jurist | Statement: [Quaestiones, juristRankOfAuthor, eminent jurist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juristRankOfAuthor Context triple: [Quaestiones, juristRankOfAuthor, eminent jurist]
-
A.
authorRank
Indicates the relative standing or position of an author within a ranked ordering, such as by contribution, importance, or prominence.
-
B.
hasAcademicRank
Indicates that an entity holds a specific academic rank or title within an educational or research institution.
-
C.
hasJudicialRank
Indicates that an entity holds a specified level or position within a judicial or court hierarchy.
-
D.
typeOfJurist
chosen
Indicates that one entity is a specific kind or category of jurist in relation to another entity.
-
E.
legalHierarchyRank
Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.