Triple
T19680595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGR |
E472573
|
entity |
| Predicate | typicalAssignments |
P12230
|
FINISHED |
| Object | unit full-time staff positions |
—
|
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: unit full-time staff positions | Statement: [AGR, typicalAssignments, unit full-time staff positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAssignments Context triple: [AGR, typicalAssignments, unit full-time staff positions]
-
A.
assignmentType
Indicates the specific category or kind of assignment associated with an entity or activity.
-
B.
typicalStudentAssignment
Indicates that an assignment is a standard or commonly expected task given to a student in a particular educational context.
-
C.
traditionallyAssignedTo
Indicates that something is customarily or historically designated as the responsibility, role, or domain of a particular entity according to tradition.
-
D.
assignmentBasis
Indicates the criterion or rationale on which an assignment or allocation is determined.
-
E.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bf97348190bc31b00ed4ec6cad |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.