Triple
T16338845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test cricket |
E396743
|
entity |
| Predicate | isPlayedBetween |
P67856
|
FINISHED |
| Object | national representative teams |
—
|
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: national representative teams | Statement: [Test cricket, isPlayedBetween, national representative teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlayedBetween Context triple: [Test cricket, isPlayedBetween, national representative teams]
-
A.
playedBetween
chosen
Indicates that an event, game, or match occurred involving two specified entities as participants or opposing sides.
-
B.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
C.
runsBetween
Indicates a relationship where something extends, operates, or connects from one point, entity, or state to another along a path or interval.
-
D.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
E.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
- 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.