Triple
T20113656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOLE |
E490396
|
entity |
| Predicate | typicalRoleOfStudents |
P18942
|
FINISHED |
| Object | independent researchers |
—
|
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: independent researchers | Statement: [SOLE, typicalRoleOfStudents, independent researchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleOfStudents Context triple: [SOLE, typicalRoleOfStudents, independent researchers]
-
A.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalStudentOutcome
Indicates the usual or expected result, achievement, or status that students generally attain under normal conditions.
-
C.
schoolRole
Indicates the specific function, position, or capacity an entity holds within a school context (e.g., student, teacher, administrator).
-
D.
typicalStudentBackground
Indicates that an entity has the usual or commonly expected background or profile for a student in a given context.
-
E.
courseRole
Indicates the specific function or position an individual holds within a course, such as student, instructor, or assistant.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e31af081908d8e0c867c388a73 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.