Triple
T32142092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysia national bowling team |
E820930
|
entity |
| Predicate | isEliteSquad |
P173623
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Malaysia national bowling team, isEliteSquad, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEliteSquad Context triple: [Malaysia national bowling team, isEliteSquad, true]
-
A.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
B.
isFrontlineUnit
Indicates that an entity functions as a primary combat or operational unit positioned at or near the front line of engagement.
-
C.
isAboutMilitaryUnit
Indicates that something (such as a document, statement, or resource) concerns, discusses, or pertains to a specific military unit.
-
D.
isBattalionEquivalent
Indicates that one military unit has a size, role, or organizational status equivalent to that of a battalion.
-
E.
isMilitaryStaffOf
Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9aed8c881908214b59cb895fa65 |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:31 a.m.