Triple
T15312998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aristo project |
E366085
|
entity |
| Predicate | taskDomain |
P118070
|
FINISHED |
| Object | elementary school science exams |
—
|
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: elementary school science exams | Statement: [Aristo project, taskDomain, elementary school science exams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskDomain Context triple: [Aristo project, taskDomain, elementary school science exams]
-
A.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
B.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
C.
taskForce
Indicates a collaborative relationship in which multiple entities are formally grouped to work together as a specialized team on a specific task or mission.
-
D.
taskName
Indicates the specific name or label assigned to a task within a process or workflow.
-
E.
typicalTask
Indicates the kind of task or activity that is normally or characteristically performed by an entity.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd2d5a88190aead748920f93d47 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.