Triple
T1424603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan Emtage |
E30300
|
entity |
| Predicate | notablePeriodOfActivity |
P15561
|
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: [Alan Emtage, notablePeriodOfActivity, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodOfActivity Context triple: [Alan Emtage, notablePeriodOfActivity, late 1980s]
-
A.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
B.
notableYearOfActivity
Indicates the specific year during which an entity was particularly active, prominent, or notable in its activities or impact.
-
C.
historicalPeriodOfMajorActivity
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
D.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
E.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.