Triple
T10426116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stony Brook Elementary School |
E245792
|
entity |
| Predicate | hasCompulsoryAttendance |
P76724
|
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: [Stony Brook Elementary School, hasCompulsoryAttendance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompulsoryAttendance Context triple: [Stony Brook Elementary School, hasCompulsoryAttendance, yes]
-
A.
hasAttendanceType
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
B.
hasTypicalAttendance
Indicates the usual or characteristic number of attendees associated with an event, venue, or activity.
-
C.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
D.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
E.
isObligatory
chosen
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea48cb348190ad4432f263300592 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.