Triple
T26390820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | weightingRule |
P35633
|
FINISHED |
| Object | reciprocal of rank position |
—
|
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: reciprocal of rank position | Statement: [Dowdall system, weightingRule, reciprocal of rank position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightingRule Context triple: [Dowdall system, weightingRule, reciprocal of rank position]
-
A.
labelingRule
Indicates that a specified rule or criterion is used to assign a particular label or category to an entity.
-
B.
groupingRule
Indicates a rule or criterion that defines how multiple entities are grouped or clustered together based on shared characteristics or conditions.
-
C.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
D.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
E.
decisionMakingRule
chosen
Indicates the principle, guideline, or procedure that governs how a decision is made in a given context.
- 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_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 11:25 p.m.