Triple
T18841925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO project committee |
E460818
|
entity |
| Predicate | hasLifecycle |
P30392
|
FINISHED |
| Object | temporary |
—
|
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: temporary | Statement: [ISO project committee, hasLifecycle, temporary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifecycle Context triple: [ISO project committee, hasLifecycle, temporary]
-
A.
designedForLifecycle
Indicates that something has been intentionally created or configured to support, align with, or optimize a particular lifecycle or set of lifecycle stages.
-
B.
lifecycleType
chosen
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
C.
coversLifecycleStage
Indicates that one entity includes, addresses, or spans a particular stage within a defined lifecycle.
-
D.
lifecycleBehavior
Indicates how an entity behaves, changes, or is managed over the course of its existence or lifecycle.
-
E.
lifecycleTiedTo
Indicates that the existence, duration, or validity of one entity is dependent on and ends with the lifecycle of another entity.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ea35c88190af6659551ad18130 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.