Triple
T6653295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 掛布雅之 |
E150875
|
entity |
| Predicate | ドラフト種別 |
P72111
|
FINISHED |
| Object | ドラフト6位指名 |
—
|
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: ドラフト6位指名 | Statement: [掛布雅之, ドラフト種別, ドラフト6位指名]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ドラフト種別 Context triple: [掛布雅之, ドラフト種別, ドラフト6位指名]
-
A.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
B.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
C.
ABA draftRound
Indicates the specific round in which a player was selected during an ABA draft.
-
D.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
E.
draftedInto
Indicates that an entity is formally selected or conscripted to join and serve in a particular organization, group, or role, typically without initiating the choice themselves.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.