Triple
T32485740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannah Khoury |
E830234
|
entity |
| Predicate | hasRoleInSeries |
P83015
|
FINISHED |
| Object | team leadership |
—
|
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: team leadership | Statement: [Hannah Khoury, hasRoleInSeries, team leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInSeries Context triple: [Hannah Khoury, hasRoleInSeries, team leadership]
-
A.
hasWorkInSeriesRole
chosen
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
-
B.
ownershipStatusInSeries
Indicates the type or state of ownership an entity holds within a particular series or collection.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
hasGenreInSeries
Indicates that a particular genre is associated with, or applies to, a work as it appears within a specific series.
-
E.
appearsInSeriesBy
Indicates that one entity (such as a work or character) is featured within a series that is created, authored, or produced by another entity.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 12:58 a.m.