Triple
T31389908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine School of Science and Mathematics |
E800702
|
entity |
| Predicate | residentialProgram |
P44568
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maine School of Science and Mathematics, residentialProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialProgram Context triple: [Maine School of Science and Mathematics, residentialProgram, yes]
-
A.
hasResidentialProgram
chosen
Indicates that an entity offers or is associated with a residential program where participants live on-site.
-
B.
hadResidentialProgram
Indicates that an entity operated or offered a residential program in which participants lived on-site for a period of time.
-
C.
supportingProgram
Indicates that one program provides assistance, resources, or backing to another program or initiative.
-
D.
residentialCampus
Indicates that an educational institution’s campus includes on-site housing where students live as part of the campus community.
-
E.
primaryProgram
Indicates that one entity serves as the main or principal program associated with another entity, distinguishing it from any secondary or auxiliary programs.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.