Triple
T23349258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World's Finest Comics |
E591959
|
entity |
| Predicate | pageCountCharacteristic |
P9415
|
FINISHED |
| Object | 80-page giant (early issues) |
—
|
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: 80-page giant (early issues) | Statement: [World's Finest Comics, pageCountCharacteristic, 80-page giant (early issues)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pageCountCharacteristic Context triple: [World's Finest Comics, pageCountCharacteristic, 80-page giant (early issues)]
-
A.
hasPageCountApprox
chosen
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
-
B.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
C.
numberOfSheets
Indicates the quantity of individual sheets associated with or contained in an entity.
-
D.
codePageNumber
Indicates the specific page number within a code document or code listing where something is located or referenced.
-
E.
linesPerPage
Indicates the number of lines that are contained or displayed on a single page.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f199cb2a3c8190a5c0c8d8735256c7 |
completed | April 29, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.