Triple
T17681599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Essay |
E440782
|
entity |
| Predicate | supervisorRole |
P9418
|
FINISHED |
| Object | guidance and monitoring |
—
|
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: guidance and monitoring | Statement: [Extended Essay, supervisorRole, guidance and monitoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisorRole Context triple: [Extended Essay, supervisorRole, guidance and monitoring]
-
A.
supervisesFor
Indicates that one entity oversees, directs, or manages the work, activities, or responsibilities of another entity on behalf of a third party or specific purpose.
-
B.
canSupervise
chosen
Indicates that one entity has the authority or capability to oversee, direct, or manage the work or activities of another entity.
-
C.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
D.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
-
E.
roleInAdministration
Indicates that an entity holds a specific position or function within an administrative structure or governing body.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e470445b3881908bb0930b986089f7 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.