Triple
T17788912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolyn Strauss |
E444097
|
entity |
| Predicate | roleInGameOfThrones |
P62891
|
FINISHED |
| Object | executive producer |
—
|
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: executive producer | Statement: [Carolyn Strauss, roleInGameOfThrones, executive producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGameOfThrones Context triple: [Carolyn Strauss, roleInGameOfThrones, executive producer]
-
A.
GameOfThronesRole
chosen
Indicates that one entity plays, voices, or otherwise portrays a character in the television series "Game of Thrones" in relation to another entity.
-
B.
roleInWarOfTheRing
Indicates the specific function, position, or involvement an entity had within the events of the War of the Ring.
-
C.
roleForVarys
Indicates that a particular role, position, or function is assigned to or associated with Varys.
-
D.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
E.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879524bc819090855ab5248c73db |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.