Triple
T26390824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | nthPreferenceWeight |
P6679
|
FINISHED |
| Object | 1/n |
—
|
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: 1/n | Statement: [Dowdall system, nthPreferenceWeight, 1/n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nthPreferenceWeight Context triple: [Dowdall system, nthPreferenceWeight, 1/n]
-
A.
priorityDeterminedBy
Indicates that the priority or importance level of one entity is established based on another entity or set of factors.
-
B.
priorityRule
Indicates that one entity is given precedence or higher processing order over another according to a defined rule or policy.
-
C.
isHeavilyWeightedToward
Indicates that something is strongly biased or disproportionately oriented in favor of one side, option, or aspect over others.
-
D.
isLessPreferredBy
Indicates that one option, item, or entity is chosen or favored less than another by a particular agent or group.
-
E.
weightingMethod
chosen
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
- 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.