Triple
T28307498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Rowley |
E713901
|
entity |
| Predicate | hasTitleCharacterIn |
P91787
|
FINISHED |
| Object | Red Shift |
—
|
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: Red Shift | Statement: [Thomas Rowley, hasTitleCharacterIn, Red Shift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterIn Context triple: [Thomas Rowley, hasTitleCharacterIn, Red Shift]
-
A.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
-
B.
hasTitleLetter
chosen
Indicates that an entity possesses a specific letter or character within its title.
-
C.
hasTitleCharacterAction
Indicates that a work’s title explicitly references or is derived from an action performed by a character within that work.
-
D.
isTitleCharacterString
Indicates that a given string represents the title text associated with an entity.
-
E.
hasMainTitleCharacter
Indicates that a work’s primary or main title is centered on, derived from, or explicitly names a particular character.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 11:38 p.m.