Triple
T32376087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop |
E827286
|
entity |
| Predicate | professionalNameOf |
P103813
|
FINISHED |
| Object | Andrew "Pop" Wansel |
—
|
NE NERFINISHED |
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: Andrew "Pop" Wansel | Statement: [Pop, professionalNameOf, Andrew "Pop" Wansel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionalNameOf Context triple: [Pop, professionalNameOf, Andrew "Pop" Wansel]
-
A.
professionalName
chosen
Indicates the formal name or title an entity uses in a professional or occupational context.
-
B.
professionalCategory
Indicates the classification of an entity according to its professional field, role, or occupational domain.
-
C.
professionalBase
Indicates that one entity serves as the primary professional location, organization, or base of operations for another entity.
-
D.
professionalWins
Indicates that one entity has achieved a certain number of victories or successes in a professional context, such as in a career, competition, or formal domain.
-
E.
professionalBody
Indicates that an entity is a formal organization that represents, regulates, or supports members of a particular profession.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:50 a.m.