Triple
T17904989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Huston |
E447677
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Huston |
—
|
NE NERFINISHED |
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: Huston | Statement: [Jack Huston, familyName, Huston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huston Context triple: [Jack Huston, familyName, Huston]
-
A.
Huston
chosen
Huston is a surname most famously associated with a prominent American film family that includes acclaimed director John Huston and actress Anjelica Huston.
-
B.
Henderson
Henderson is a small city in north-central North Carolina that serves as the administrative and commercial hub of Vance County.
-
C.
Henderson
Henderson is a major city in the Las Vegas metropolitan area known for its rapid growth, residential communities, and proximity to the Las Vegas Strip.
-
D.
Henderson
Henderson is a common English and Scottish surname derived from "son of Henry," borne by numerous notable individuals across various fields.
-
E.
Henderson
Henderson is the fictional Midwestern town that serves as the primary setting for the long-running American soap opera "Search for Tomorrow."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9b643c8190a01e9ec4caa88183 |
completed | April 19, 2026, 9:21 a.m. |
Created at: April 10, 2026, 10:19 a.m.