Triple
T8319587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thumbprint |
E194794
|
entity |
| Predicate | comicAdaptationIssueCount |
P81922
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Thumbprint, comicAdaptationIssueCount, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicAdaptationIssueCount Context triple: [Thumbprint, comicAdaptationIssueCount, 3]
-
A.
hasComicSeries
Indicates that one entity is the comic series to which another entity belongs or with which it is associated.
-
B.
hasFictionalIssue
Indicates that one entity possesses, is associated with, or is characterized by a particular fictional problem, flaw, or complication.
-
C.
comicFunction
Indicates a relationship where something serves a humorous or entertainment role, such as providing comedy, comic relief, or a joking purpose within a context.
-
D.
seriesNumberInAdventureSeries
Indicates the position or installment number that an item occupies within an adventure series.
-
E.
comicPublisher
Indicates that one entity is the publisher responsible for producing or distributing the comic associated with another entity.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f6686a0819094abc2bfd2e500a5 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 5:55 p.m.