Triple
T2309588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dioscorus |
E51920
|
entity |
| Predicate | statusInScholarship |
P6978
|
FINISHED |
| Object | possibly legendary or non-historical |
—
|
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: possibly legendary or non-historical | Statement: [Dioscorus, statusInScholarship, possibly legendary or non-historical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInScholarship Context triple: [Dioscorus, statusInScholarship, possibly legendary or non-historical]
-
A.
scholarshipType
Indicates the specific category or kind of scholarship associated with an entity.
-
B.
scholarshipEquivalency
Indicates that one scholarship is considered equal in value, coverage, or benefit to another scholarship or financial award.
-
C.
hasScholarships
Indicates that an entity provides, offers, or is associated with one or more scholarships to another entity.
-
D.
academicStatus
chosen
Indicates the educational or scholarly standing or level an entity holds within an academic context.
-
E.
associatedScholarship
Indicates a relationship where a scholarship is linked or connected to a particular entity (such as a person, program, or institution).
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.