Triple
T37016699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tale of the Cat |
E916100
|
entity |
| Predicate | gradeLevelOfNotableWin |
P111111
|
FINISHED |
| Object | Grade I |
—
|
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: Grade I | Statement: [Tale of the Cat, gradeLevelOfNotableWin, Grade I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeLevelOfNotableWin Context triple: [Tale of the Cat, gradeLevelOfNotableWin, Grade I]
-
A.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
B.
notableWinType
chosen
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
-
C.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
D.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
E.
notablePlayerWinningTeam
Indicates that a particular notable player was a member of the team that won a given competition or game.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:14 p.m.