Triple
T31568778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Lee |
E805493
|
entity |
| Predicate | 2TimesReleasePeriod |
P173444
|
FINISHED |
| Object | late 1990s |
—
|
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 1990s | Statement: [Ann Lee, 2TimesReleasePeriod, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2TimesReleasePeriod Context triple: [Ann Lee, 2TimesReleasePeriod, late 1990s]
-
A.
2TimesType
Indicates a relationship where one quantity, event, or type occurs at exactly twice the amount, frequency, or magnitude of another.
-
B.
secondCyclePeriod
Indicates the duration or interval of time associated with a second occurrence or cycle of a recurring process or event.
-
C.
typicalReEntryPeriod
Indicates the usual or standard amount of time that typically passes before something returns, reoccurs, or re-enters a given state, context, or system.
-
D.
secondMintingPeriodStart
Indicates the point in time when the second minting period for an asset or token begins.
-
E.
workReleasePeriod
Indicates the time span during which a person is authorized to leave confinement or regular duties to perform work under a work-release arrangement.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 30, 2026, 10:18 p.m.