Triple
T26985674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiln People |
E679729
|
entity |
| Predicate | copyLifespan |
P585
|
FINISHED |
| Object | one day |
—
|
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: one day | Statement: [Kiln People, copyLifespan, one day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copyLifespan Context triple: [Kiln People, copyLifespan, one day]
-
A.
supportsLifespan
Indicates that one entity contributes to maintaining, extending, or enabling the full duration of another entity’s life or functional existence.
-
B.
sourceForLifespan
Indicates that one entity serves as the reference or authority providing information about the lifespan of another entity.
-
C.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
-
D.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
E.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6215954f8819092cf882ca976fafa |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:48 a.m.