Triple
T15992460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Henwick |
E387866
|
entity |
| Predicate | playedCharacter |
P1507
|
FINISHED |
| Object | Alex |
E50009
|
NE 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: Alex | Statement: [Jessica Henwick, playedCharacter, Alex]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alex Context triple: [Jessica Henwick, playedCharacter, Alex]
-
A.
Alex
chosen
Alex is a common given name, typically used as a shortened form of Alexander or Alexandra.
-
B.
Alan
Alan is a masculine given name of Celtic origin that has been widely used in English-speaking countries.
-
C.
Alan
The Alans were an ancient nomadic Iranian-speaking people of the Eurasian steppes, known for their skilled horsemanship and significant role in the migrations that shaped late antiquity Europe.
-
D.
Andrew
Andrew is a masculine given name of Greek origin meaning "manly" or "brave," widely used in English-speaking countries and beyond.
-
E.
Andrew
Andrew is a subway station in South Boston on the Massachusetts Bay Transportation Authority's Red Line.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157844ed881908b42bfc1bb740d4e |
completed | April 16, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3d3ef2881909213ff608192f1ef |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:54 a.m.