Triple
T28897875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sketch Turner |
E732876
|
entity |
| Predicate | pulledInto |
P33453
|
FINISHED |
| Object | his own comic book world |
—
|
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: his own comic book world | Statement: [Sketch Turner, pulledInto, his own comic book world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pulledInto Context triple: [Sketch Turner, pulledInto, his own comic book world]
-
A.
enteredInto
Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
-
B.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
-
C.
broughtTo
chosen
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
D.
takenInBy
Indicates that one entity is absorbed, ingested, or otherwise brought inside and contained by another entity.
-
E.
enteredIntoForceIn
Indicates that an agreement, law, or treaty became legally effective or operative in a specified place or jurisdiction.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa5b40881908123b73bb40b1526 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8 a.m.