Triple
T26390836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | favoringProperty |
P12179
|
FINISHED |
| Object | consensus candidates |
—
|
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: consensus candidates | Statement: [Dowdall system, favoringProperty, consensus candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: favoringProperty Context triple: [Dowdall system, favoringProperty, consensus candidates]
-
A.
favored
chosen
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
B.
usesProp
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
C.
eligibleProperties
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
D.
parityProperty
Indicates that a relationship or quantity has a specific parity (such as being even, odd, or matching in parity) according to the defined property.
-
E.
basisProperty
Indicates that one property serves as the foundational or defining basis for another property or characteristic.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bf1e248190a186aed862513478 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:25 p.m.