Triple
T33127293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naṣībīn |
E847754
|
entity |
| Predicate | hasEducationHistory |
P37641
|
FINISHED |
| Object | site of the School of Nisibis |
—
|
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: site of the School of Nisibis | Statement: [Naṣībīn, hasEducationHistory, site of the School of Nisibis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEducationHistory Context triple: [Naṣībīn, hasEducationHistory, site of the School of Nisibis]
-
A.
hasHigherEducationHistory
Indicates that an entity has a record of having pursued or completed higher education studies in the past.
-
B.
hasSchoolTypeHistory
Indicates that an entity has an associated record or timeline of changes in its school type over time.
-
C.
educationHistory
chosen
Indicates that an entity has a record of formal learning experiences or academic qualifications associated with it.
-
D.
hasEducationIn
Indicates that an entity has received education, training, or formal study in a specified field, subject, or discipline.
-
E.
hasEducationalStatus
Indicates that an entity possesses a particular level, state, or condition of formal education or academic attainment.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:27 a.m.