Triple
T36390759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Many Clouds |
E896319
|
entity |
| Predicate | fameWithinSport |
P5150
|
FINISHED |
| Object | leading staying chaser |
—
|
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: leading staying chaser | Statement: [Many Clouds, fameWithinSport, leading staying chaser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fameWithinSport Context triple: [Many Clouds, fameWithinSport, leading staying chaser]
-
A.
knownForSports
chosen
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
isFollowedInSportsBy
Indicates that one entity succeeds or comes after another in a sports-related context, such as in rankings, events, or sequences.
-
D.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
E.
sportsIdentity
Indicates that an entity’s identity, role, or affiliation is defined in the context of sports (e.g., as an athlete, team, or sports-related organization).
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.