Triple
T3320357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durantula |
E69779
|
entity |
| Predicate | appliesToProfession |
P35215
|
FINISHED |
| Object | basketball player |
—
|
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: basketball player | Statement: [Durantula, appliesToProfession, basketball player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToProfession Context triple: [Durantula, appliesToProfession, basketball player]
-
A.
recognizesProfession
Indicates that one entity acknowledges or identifies another entity’s professional role or occupation as such.
-
B.
isAssociatedWithProfessionOfBearer
chosen
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
E.
professionServed
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13a4e948190841134d6ae6ef432 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.