Triple
T22717744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubagio |
E561778
|
entity |
| Predicate | hasLongHalfLife |
P38026
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aubagio, hasLongHalfLife, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongHalfLife Context triple: [Aubagio, hasLongHalfLife, true]
-
A.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
hasEliminationHalfLife
chosen
Indicates the duration required for half of a substance or entity to be removed, degraded, or rendered inactive within a given system or context.
-
C.
longLived
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
-
D.
hasLongHistory
Indicates that the relationship or subject has existed or persisted over a long period of time.
-
E.
hasLong
Indicates that an entity possesses or exhibits a great extent or duration in some measurable dimension (such as length or time).
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ecbc48190926d16b20b674dbd |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.