Triple
T5007589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy |
E112533
|
entity |
| Predicate | subjectOfDiscipline |
P36625
|
FINISHED |
| Object | Classical studies |
—
|
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: Classical studies | Statement: [Troy, subjectOfDiscipline, Classical studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfDiscipline Context triple: [Troy, subjectOfDiscipline, Classical studies]
-
A.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
B.
governingDiscipline
Indicates that one discipline or field provides the primary rules, principles, or framework that regulate or guide another activity, domain, or practice.
-
C.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
D.
hasSubjectOfStudy
chosen
Indicates that an entity (such as a person or organization) focuses on, researches, or specializes in a particular field or topic of study.
-
E.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.