Triple
T28566680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missy Cooper |
E722697
|
entity |
| Predicate | academicAbilityRelativeToSheldon |
P164879
|
FINISHED |
| Object | less academically gifted |
—
|
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: less academically gifted | Statement: [Missy Cooper, academicAbilityRelativeToSheldon, less academically gifted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicAbilityRelativeToSheldon Context triple: [Missy Cooper, academicAbilityRelativeToSheldon, less academically gifted]
-
A.
hasIQ
Indicates that an entity possesses a specific intelligence quotient (IQ) value or score.
-
B.
hasHighIQ
Indicates that an entity possesses an intelligence level above a specified high threshold.
-
C.
schoolSubjectStrength
Indicates a relationship where an entity has a particular level of ability or proficiency in a specific school subject.
-
D.
typeOfIntelligence
Indicates that one entity is a specific kind or category of intelligence in relation to another entity.
-
E.
targetStudentAbility
Indicates a relationship where a target student possesses, demonstrates, or is characterized by a particular ability or skill.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:07 a.m.