Triple
T34011481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Mountstuart |
E872123
|
entity |
| Predicate | lifeSpanCoverage |
P162481
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Logan Mountstuart, lifeSpanCoverage, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeSpanCoverage Context triple: [Logan Mountstuart, lifeSpanCoverage, 20th century]
-
A.
lifeCycleCoverage
Indicates that one entity addresses, spans, or is applicable across specific stages or the entirety of another entity’s lifecycle.
-
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.
lifespanClaim
chosen
Indicates that there is a stated or asserted duration of existence (lifespan) associated with an entity.
-
E.
providesLongDurationCoverageOver
Indicates that one entity offers protection, service, or support to another for an extended or long-term period.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.