Triple
T33535875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Greaney |
E858919
|
entity |
| Predicate | writesCharacter |
P177417
|
FINISHED |
| Object | Jack Ryan Jr. |
—
|
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: Jack Ryan Jr. | Statement: [Mark Greaney, writesCharacter, Jack Ryan Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writesCharacter Context triple: [Mark Greaney, writesCharacter, Jack Ryan Jr.]
-
A.
writtenWithCharacter
Indicates that something is written using a particular character or set of characters as its writing system or notation.
-
B.
writtenForCharacter
Indicates that a piece of writing (such as a script, scene, or dialogue) was specifically created or tailored for a particular character.
-
C.
writesSystem
Indicates that an entity authors or produces a system, such as designing, coding, or otherwise creating it.
-
D.
writingOutput
Indicates that one entity produces or generates written content as an output, typically as the result of a writing or text-creation process.
-
E.
hasWriterCharacter
Indicates that a writer is a character within a work, linking the work to the character who serves as its writer.
- F. None of above. chosen
Provenance (4 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:39 a.m.