Triple
T26343906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Opium Intense |
E662724
|
entity |
| Predicate | longevityDescription |
P160429
|
FINISHED |
| Object | long-lasting |
—
|
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: long-lasting | Statement: [Black Opium Intense, longevityDescription, long-lasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longevityDescription Context triple: [Black Opium Intense, longevityDescription, long-lasting]
-
A.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
leafLongevity
Indicates the duration for which a leaf remains alive and functional before it senesces or is shed.
-
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.
lifeExtensionGoal
Indicates an intention or objective to prolong the lifespan or extend the duration of life beyond its current or natural limits.
-
E.
lifetimeInGenerations
Indicates the number of successive generations over which something (e.g., an effect, trait, or validity) persists or remains applicable.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa593688190af7f148b5ee6ce51 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:41 p.m.