Triple
T8095835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhimov Naval School |
E188981
|
entity |
| Predicate | hasStudentBodyDesignation |
P5246
|
FINISHED |
| Object | cadets |
—
|
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: cadets | Statement: [Nakhimov Naval School, hasStudentBodyDesignation, cadets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentBodyDesignation Context triple: [Nakhimov Naval School, hasStudentBodyDesignation, cadets]
-
A.
hasStudentBodyFrom
Indicates that an educational institution draws or enrolls its student body from a specified geographic area, group, or source.
-
B.
hasStudentBodyType
chosen
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
C.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
D.
hasEducationalDesignation
Indicates that an entity holds a specific educational title, status, or classification assigned by an educational system or institution.
-
E.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4291f1d4819098985ac2b20b6c75 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.