Triple
T30936740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmett Mann |
E788141
|
entity |
| Predicate | activePeriodAsSubject |
P150217
|
FINISHED |
| Object | late 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: late 1980s | Statement: [Emmett Mann, activePeriodAsSubject, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activePeriodAsSubject Context triple: [Emmett Mann, activePeriodAsSubject, late 1980s]
-
A.
activeWithin
Indicates that an entity operates, functions, or remains valid inside a specified spatial, temporal, or contextual boundary.
-
B.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
C.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
D.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
E.
mainSubjectPeriod
chosen
Indicates the time period during which the subject served as the primary or main focus, role, or activity.
- F. None of above.
Provenance (3 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 8:52 p.m.