Triple
T26209447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cricket |
E655443
|
entity |
| Predicate | hasPrimaryScoringUnit |
P174682
|
FINISHED |
| Object | run |
—
|
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: run | Statement: [Cricket, hasPrimaryScoringUnit, run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryScoringUnit Context triple: [Cricket, hasPrimaryScoringUnit, run]
-
A.
hasScoringUnit
chosen
Indicates that one entity possesses or is associated with a unit used for scoring, measurement, or point allocation in a given context.
-
B.
scoringUnit
Indicates that one entity functions as a unit or component responsible for scoring or assigning scores to another entity.
-
C.
hasScorecardUnit
Indicates that one entity is associated with a specific scorecard unit used for measuring or evaluating its performance or outcomes.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
hasPrimaryConstituent
Indicates that one entity serves as the main or principal component, ingredient, or element 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 26, 2026, 8:51 p.m.