Triple
T26209587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Arab Emirates national cricket team |
E655446
|
entity |
| Predicate | ListAStatus |
P15010
|
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: [United Arab Emirates national cricket team, ListAStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ListAStatus Context triple: [United Arab Emirates national cricket team, ListAStatus, yes]
-
A.
listedStatus
Indicates that an entity has an official listing designation or status within a defined registry, catalog, or classification system.
-
B.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
C.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
D.
hasStatusIn
chosen
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
E.
targetsStatus
Indicates that one entity directs its actions or focus toward another entity based on the latter’s current status or condition.
- 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_69f60d160f60819087ee6aac626327ea |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:52 p.m.