Triple
T4619449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calmecac |
E100941
|
entity |
| Predicate | studentsWere |
P43375
|
FINISHED |
| Object | children of nobles |
—
|
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: children of nobles | Statement: [Calmecac, studentsWere, children of nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentsWere Context triple: [Calmecac, studentsWere, children of nobles]
-
A.
studentsPerformAt
Indicates that students carry out or present a performance, activity, or task at a particular event, venue, or context.
-
B.
studentsWing
Indicates a relationship where a particular wing, section, or area is designated for or associated with students.
-
C.
hasStudents
Indicates that an entity (such as a class, school, or teacher) is associated with one or more students.
-
D.
notableStudent
Indicates that a person is a distinguished or particularly significant student of another individual or institution.
-
E.
notableStudentBodyAssociatedWith
chosen
Indicates that there is a significant or noteworthy group of students associated with a particular entity, such as an institution, organization, or program.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.