Triple
T8268167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard Wolowitz |
E193352
|
entity |
| Predicate | roleOnShow |
P17747
|
FINISHED |
| Object | main character |
—
|
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: main character | Statement: [Howard Wolowitz, roleOnShow, main character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnShow Context triple: [Howard Wolowitz, roleOnShow, main character]
-
A.
displayRole
chosen
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
B.
roleDependsOn
Indicates that the existence, behavior, or permissions of one role are contingent upon or derived from another role.
-
C.
visibilityRole
Indicates the role or level of access an entity has in determining what information or content is visible to others.
-
D.
catalogRole
Indicates that an entity holds a specific functional role or responsibility within the context of a catalog or cataloging system.
-
E.
roleInAppointments
Indicates the specific function or capacity an entity holds within one or more scheduled appointments.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794fc4208190b268bc69ff2b28a9 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.