Triple
T3726467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K Line |
E81760
|
entity |
| Predicate | hasAtGradeSection |
P44491
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [K Line, hasAtGradeSection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtGradeSection Context triple: [K Line, hasAtGradeSection, true]
-
A.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
B.
hasStudentSection
Indicates that an entity (such as a course or class) is associated with a specific student section or subgroup of enrolled students.
-
C.
hasGradeCount
Indicates a relationship where an entity is associated with the number of grades it has or has received.
-
D.
isAtGrade
chosen
Indicates that an entity is positioned at or corresponds to a specific grade or level within an ordered scale or classification.
-
E.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf669d48190852aaeef70265404 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.