Triple
T29542212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonina |
E749533
|
entity |
| Predicate | lifePeriodCovered |
P3058
|
FINISHED |
| Object | several decades |
—
|
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: several decades | Statement: [Antonina, lifePeriodCovered, several decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifePeriodCovered Context triple: [Antonina, lifePeriodCovered, several decades]
-
A.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
lifetimeCovers
Indicates that a specified coverage, policy, or protection applies for the entire duration of an entity’s existence or validity, without temporal gaps or renewals.
-
C.
lifetimeCovers
Indicates that a coverage, warranty, or protection remains valid for the entire lifetime of the specified subject or item.
-
D.
lifeCycleCoverage
Indicates that one entity addresses, spans, or is applicable across specific stages or the entirety of another entity’s lifecycle.
-
E.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ccb2f0c8190afec245ff546681c |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:03 p.m.