Triple
T16338889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test cricket |
E396743
|
entity |
| Predicate | battingMilestones |
P96361
|
FINISHED |
| Object | century |
—
|
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: century | Statement: [Test cricket, battingMilestones, century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingMilestones Context triple: [Test cricket, battingMilestones, century]
-
A.
battingMilestone
chosen
Indicates reaching a significant achievement or benchmark related to batting performance, such as a notable run total or record.
-
B.
baseballAchievement
Indicates that an entity has attained a notable accomplishment, record, or honor specifically within the context of baseball.
-
C.
notableBattingInnovation
Indicates that an entity is recognized for introducing or significantly contributing to an important innovation in batting technique, strategy, or equipment.
-
D.
homeRunLeaders
Indicates the relationship where certain players are identified as having the highest number of home runs, typically within a given league, season, or time span.
-
E.
fieldingMilestone
Indicates a notable achievement or benchmark reached in a player's defensive or fielding performance.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.