Triple
T7264708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle school |
E159741
|
entity |
| Predicate | studentGrouping |
P68005
|
FINISHED |
| Object | by grade level |
—
|
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: by grade level | Statement: [Middle school, studentGrouping, by grade level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentGrouping Context triple: [Middle school, studentGrouping, by grade level]
-
A.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
B.
studentSection
Indicates a relationship where a student is enrolled in or associated with a particular course section.
-
C.
studentComposition
chosen
Indicates that one entity is composed of or consists of students, specifying a part-whole relationship where students collectively form the other entity.
-
D.
targetStudentGroup
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
E.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.