Triple
T4765241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paxos consensus algorithm |
E105793
|
entity |
| Predicate | livenessProperty |
P59187
|
FINISHED |
| Object | eventual decision under sufficient synchrony |
—
|
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: eventual decision under sufficient synchrony | Statement: [Paxos consensus algorithm, livenessProperty, eventual decision under sufficient synchrony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livenessProperty Context triple: [Paxos consensus algorithm, livenessProperty, eventual decision under sufficient synchrony]
-
A.
isLiving
Indicates that an entity is currently alive or possesses life.
-
B.
lifecycleStatus
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
C.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
D.
hasLivingParent
Indicates that an entity has at least one parent who is currently alive.
-
E.
hasSurvivalStatus
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd686dc7b88190b41e8a362701080d |
completed | March 20, 2026, 3:31 p.m. |
Created at: March 20, 2026, 1:21 p.m.