Triple
T4765272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paxos consensus algorithm |
E105793
|
entity |
| Predicate | messagePattern |
P8034
|
FINISHED |
| Object | two-round protocol in basic form |
—
|
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: two-round protocol in basic form | Statement: [Paxos consensus algorithm, messagePattern, two-round protocol in basic form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messagePattern Context triple: [Paxos consensus algorithm, messagePattern, two-round protocol in basic form]
-
A.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
B.
intendedMessage
Indicates that one entity is the message or content that another entity aims or plans to communicate.
-
C.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
D.
bodyPattern
Indicates a recurring or characteristic configuration, arrangement, or sequence exhibited by a body or physical form.
-
E.
moduloPatternName
Indicates that an entity is associated with a specific naming pattern used for modulo-based grouping or partitioning.
- 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_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. |
Created at: March 20, 2026, 1:21 p.m.