Triple
T1384454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses Malone |
E29811
|
entity |
| Predicate | allDefensiveTeamSelections |
P11647
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Moses Malone, allDefensiveTeamSelections, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allDefensiveTeamSelections Context triple: [Moses Malone, allDefensiveTeamSelections, 2]
-
A.
AllDefensiveSelection
Indicates that an entity has been chosen for inclusion on an all-defensive team or recognized for outstanding defensive performance within a competitive context.
-
B.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
C.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
D.
NBAAllDefensiveTeamSelections
chosen
Indicates the number of times an entity has been selected to an NBA All-Defensive Team.
-
E.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33896548190b44f70c9aaaed9b6 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.