Triple
T21980300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men at Work: The Craft of Baseball |
E542818
|
entity |
| Predicate | profileRole |
P146141
|
FINISHED |
| Object | manager |
—
|
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: manager | Statement: [Men at Work: The Craft of Baseball, profileRole, manager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: profileRole Context triple: [Men at Work: The Craft of Baseball, profileRole, manager]
-
A.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
B.
profileType
Indicates the specific category or role classification assigned to a profile within a system.
-
C.
socialRoleIn
Indicates that one entity holds a particular social role, status, or position within the context or framework defined by another entity.
-
D.
providedRole
Indicates that one entity has assigned or supplied a specific role or function to another entity.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248cf0388190b557d065beb662b5 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:04 p.m.