Triple
T25455246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corps des Pages |
E637896
|
entity |
| Predicate | studentsHeldTitle |
P158841
|
FINISHED |
| Object | page |
—
|
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: page | Statement: [Corps des Pages, studentsHeldTitle, page]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentsHeldTitle Context triple: [Corps des Pages, studentsHeldTitle, page]
-
A.
studentsReceive
Indicates that one or more students are the recipients of something, such as instruction, resources, or communications, from another source.
-
B.
studentsStatus
Indicates the current academic or enrollment status associated with one or more students.
-
C.
studentsPerformAt
Indicates that students carry out or present a performance, activity, or task at a particular event, venue, or context.
-
D.
notableStudent
Indicates that a person is a distinguished or particularly significant student of another individual or institution.
-
E.
notableStudentBodyAssociatedWith
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. chosen
Provenance (4 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f725e4d08190b0304e45a417193b |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 2:04 p.m.