Triple
T1080359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze Ball |
E23930
|
entity |
| Predicate | relativeRankingToGoldenBall |
P22893
|
FINISHED |
| Object | below Golden Ball |
—
|
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: below Golden Ball | Statement: [Bronze Ball, relativeRankingToGoldenBall, below Golden Ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeRankingToGoldenBall Context triple: [Bronze Ball, relativeRankingToGoldenBall, below Golden Ball]
-
A.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
B.
rankComparedTo
chosen
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
C.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
rankedAmong
Indicates that an entity holds a specific position or status within a defined group, list, or hierarchy of comparable entities.
-
E.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94509d08190964509ea4a2d7912 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.