Triple
T28670623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Junior Circuit |
E725707
|
entity |
| Predicate | administersRanking |
P104357
|
FINISHED |
| Object | ITF Junior World Ranking |
—
|
NE NERFINISHED |
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: ITF Junior World Ranking | Statement: [ITF Junior Circuit, administersRanking, ITF Junior World Ranking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administersRanking Context triple: [ITF Junior Circuit, administersRanking, ITF Junior World Ranking]
-
A.
hasRankingSystemManagedBy
chosen
Indicates that a ranking system is overseen, controlled, or administered by a specified managing entity.
-
B.
maintainsRanking
Indicates that one entity preserves or keeps another entity’s position or level within a ranking or ordered list.
-
C.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
D.
classRank
Indicates the relative academic standing or position of an entity within a class or cohort based on performance or criteria.
-
E.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 5:03 a.m.