Triple
T35706822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branch Normal School |
E1031739
|
entity |
| Predicate | hasFormerStudentBodyType |
P136697
|
FINISHED |
| Object | coeducational |
—
|
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: coeducational | Statement: [Branch Normal School, hasFormerStudentBodyType, coeducational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerStudentBodyType Context triple: [Branch Normal School, hasFormerStudentBodyType, coeducational]
-
A.
hasFormerInstitutionType
Indicates that an entity was previously associated with or classified under a particular type of institution.
-
B.
hasStudentBodyFrom
Indicates that an educational institution draws or enrolls its student body from a specified geographic area, group, or source.
-
C.
hasSchoolTypeHistory
chosen
Indicates that an entity has an associated record or timeline of changes in its school type over time.
-
D.
hasFormerPupilRole
Indicates that an entity previously held the role or position of a pupil or student in relation to another entity.
-
E.
hasStudentBodyType
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.