Triple
T20622542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Googy |
E506735
|
entity |
| Predicate | notableWorkPeriodWithMisfits |
P140812
|
FINISHED |
| Object | early 1980s |
—
|
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: early 1980s | Statement: [Arthur Googy, notableWorkPeriodWithMisfits, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkPeriodWithMisfits Context triple: [Arthur Googy, notableWorkPeriodWithMisfits, early 1980s]
-
A.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
B.
notableWorkPeriodStart
Indicates the point in time when an entity’s period of producing its notable work or works begins.
-
C.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
D.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
E.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe25c208190af057bcd1aa6219d |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.