Triple
T20968075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chen Long |
E516421
|
entity |
| Predicate | hasBeenRanked |
P76342
|
FINISHED |
| Object | world No. 1 in men's singles by the BWF |
—
|
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: world No. 1 in men's singles by the BWF | Statement: [Chen Long, hasBeenRanked, world No. 1 in men's singles by the BWF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenRanked Context triple: [Chen Long, hasBeenRanked, world No. 1 in men's singles by the BWF]
-
A.
isRanked
chosen
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
B.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
C.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
D.
hasRankingStrength
Indicates the relative strength or priority of an entity’s ranking compared to others in a given ordering or evaluation.
-
E.
hasRankingFactor
Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb9d6b548190af7214ad2468cfbf |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:39 p.m.