Triple
T1195044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishwara Glassman Chrein |
E25648
|
entity |
| Predicate | typeOfBusinessPerson |
P11881
|
FINISHED |
| Object | sports club executive |
—
|
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: sports club executive | Statement: [Ishwara Glassman Chrein, typeOfBusinessPerson, sports club executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBusinessPerson Context triple: [Ishwara Glassman Chrein, typeOfBusinessPerson, sports club executive]
-
A.
personnelType
chosen
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
C.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
D.
organizationType
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
E.
legalPersonality
Indicates that an entity possesses recognized legal status, enabling it to hold rights, bear obligations, and act as a subject under the law.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd78f61c8190bdba2255d35a8fe4 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.