Triple
T34398350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byron Thames |
E882897
|
entity |
| Predicate | hasNotableWorkPeriod |
P153894
|
FINISHED |
| Object | child performer in film |
—
|
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: child performer in film | Statement: [Byron Thames, hasNotableWorkPeriod, child performer in film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWorkPeriod Context triple: [Byron Thames, hasNotableWorkPeriod, child performer in film]
-
A.
hasNotableWorkSection
Indicates that a notable work is associated with a specific section or part of a larger work or document.
-
B.
hasPeriodOfWorks
chosen
Indicates that an entity’s works are associated with, or belong to, a specific time period or phase.
-
C.
hasNotableWorkSetThere
Indicates that a notable work (such as a book, film, or other creative piece) is set in or takes place within the referenced location.
-
D.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
E.
hasNotableWorkRights
Indicates that an entity holds legal or recognized rights associated with a notable work, such as authorship, ownership, or usage rights.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a03213d35788190bdf04e19625b4060 |
completed | May 12, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a031ea131d48190ab0fecb48b8e2205 |
completed | May 12, 2026, 12:35 p.m. |
Created at: May 1, 2026, 1:59 a.m.