Triple
T4276775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypercorn |
E97062
|
entity |
| Predicate | supportsLifespan |
P55143
|
FINISHED |
| Object | ASGI lifespan protocol |
—
|
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: ASGI lifespan protocol | Statement: [Hypercorn, supportsLifespan, ASGI lifespan protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLifespan Context triple: [Hypercorn, supportsLifespan, ASGI lifespan protocol]
-
A.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
maximumRecordedLifespan
Indicates the greatest length of time that has ever been recorded for an individual of a given type to live.
-
D.
supportsPersistence
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
E.
durationOfUse
Indicates the length of time for which something is used or remains in use.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3501d677481909e7416a1d2b0008c |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.