Triple
T30406990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantom |
E773506
|
entity |
| Predicate | usesConsensusType |
P186467
|
FINISHED |
| Object | aBFT |
—
|
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: aBFT | Statement: [Fantom, usesConsensusType, aBFT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConsensusType Context triple: [Fantom, usesConsensusType, aBFT]
-
A.
supportsConsensus
Indicates that one entity endorses, upholds, or contributes to the achievement or maintenance of a shared agreement or collective decision among multiple parties.
-
B.
hasCurrentConsensus
Indicates that there is a presently agreed-upon or widely accepted position, judgment, or state regarding the related entities.
-
C.
consensusRole
Indicates that an entity participates in a consensus process with a specific functional role (e.g., proposer, validator, leader, or follower) within that agreement mechanism.
-
D.
notAdoptedByConsensus
Indicates that a proposal, decision, or action was not accepted or approved through a consensus-based process among the relevant parties.
-
E.
adoptedByConsensus
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 29, 2026, 8:04 p.m.