Triple
T36507659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Cup |
E899513
|
entity |
| Predicate | overs |
P185784
|
FINISHED |
| Object | unlimited overs |
—
|
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: unlimited overs | Statement: [Logan Cup, overs, unlimited overs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overs Context triple: [Logan Cup, overs, unlimited overs]
-
A.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
B.
overcomes
Indicates that one entity successfully prevails against, defeats, or gains control over another entity or opposing force.
-
C.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
D.
overlooks
Indicates that one entity has a view toward or looks out over another entity, typically from a higher or adjacent position.
-
E.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
- F. None of above. chosen
Provenance (4 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.