Triple
T8479758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Near East |
E200484
|
entity |
| Predicate | studiedByDiscipline |
P82843
|
FINISHED |
| Object | Assyriology |
—
|
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: Assyriology | Statement: [Ancient Near East, studiedByDiscipline, Assyriology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiedByDiscipline Context triple: [Ancient Near East, studiedByDiscipline, Assyriology]
-
A.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
B.
widelyStudiedIn
Indicates that something has been extensively researched, analyzed, or examined within a particular field, domain, or context.
-
C.
dimensionOfStudy
Indicates the specific field, aspect, or perspective that characterizes or structures a particular study or research activity.
-
D.
isSubjectOfStudy
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
-
E.
studiedWithin
Indicates that one entity pursued studies or academic work within the scope, context, or boundaries defined by another entity (such as an institution, program, or field).
- F. None of above. chosen
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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5232d008190ae55b982f5fc9e8b |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:12 p.m.