Triple
T18569084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Test Team Rankings |
E453830
|
entity |
| Predicate | usesTimeWeighting |
P6679
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ICC Test Team Rankings, usesTimeWeighting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTimeWeighting Context triple: [ICC Test Team Rankings, usesTimeWeighting, yes]
-
A.
usesTimingRules
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
-
B.
isHeavilyWeightedToward
Indicates that something is strongly biased or disproportionately oriented in favor of one side, option, or aspect over others.
-
C.
usesExtraTime
Indicates that an entity makes use of additional time beyond an initial or standard allotted period to perform or complete an action.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
weightingMethod
chosen
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b0075a08190a5d590d36089ca1e |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.