Triple
T22850692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pena |
E566346
|
entity |
| Predicate | playerTitle |
P23283
|
FINISHED |
| Object | pena khongba (traditional term for performer) |
—
|
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: pena khongba (traditional term for performer) | Statement: [Pena, playerTitle, pena khongba (traditional term for performer)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerTitle Context triple: [Pena, playerTitle, pena khongba (traditional term for performer)]
-
A.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
B.
epithetOrTitle
chosen
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
C.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
D.
coachTitle
Indicates the formal title or designation held by a coach in relation to a team, organization, or role.
-
E.
mastersTitles
Indicates that one entity holds one or more master's degree titles associated with another entity (such as an institution, field, or program).
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.