Triple
T9237070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Poor Pitiful Me |
E221963
|
entity |
| Predicate | hasNotableYear |
P87721
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Poor Poor Pitiful Me, hasNotableYear, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableYear Context triple: [Poor Poor Pitiful Me, hasNotableYear, 1977]
-
A.
hasNotablePosition
Indicates that an entity holds or has held a position, role, or office considered notable or significant.
-
B.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
C.
hasNotablePerformance
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular context.
-
D.
hasNotableRanking
Indicates that an entity holds a significant or distinguished position within an ordered list or ranking system.
-
E.
hasNotableTeamSuccess
Indicates that an entity has achieved significant or distinguished success as part of a team.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09e553081909cf864635cfc5dcc |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:29 p.m.