Triple
T31769004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greendale study group |
E810885
|
entity |
| Predicate | includesOverachiever |
P203382
|
FINISHED |
| Object | Annie Edison |
—
|
NE NERFINISHED |
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: Annie Edison | Statement: [Greendale study group, includesOverachiever, Annie Edison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOverachiever Context triple: [Greendale study group, includesOverachiever, Annie Edison]
-
A.
overarchedBy
Indicates that one entity is physically or conceptually spanned, covered, or dominated from above by another entity.
-
B.
hasBraggingRightsOver
Indicates that one entity can legitimately claim superiority or achievement over another, often as a basis for boasting.
-
C.
performsWellOn
Indicates that one entity achieves good results or high performance when evaluated using, or operating within, another entity (such as a task, test, or environment).
-
D.
mustAchieve
Indicates that an entity is required or obligated to attain or accomplish a specified goal, condition, or outcome.
-
E.
ultimatelyOvercomes
Indicates that one entity eventually defeats, surpasses, or prevails over another entity or obstacle after some progression or struggle.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a017114e7148190b7479284c316443d |
completed | May 11, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a016eebd60481909212e2a49ef95fbe |
completed | May 11, 2026, 5:53 a.m. |
| PDg | Predicate description generation | batch_6a0171143bd081909b68cca366b4dfb0 |
completed | May 11, 2026, 6:03 a.m. |
Created at: April 30, 2026, 11:33 p.m.