Triple
T10821103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girl Genius |
E255370
|
entity |
| Predicate | hasCollectedEditions |
P36864
|
FINISHED |
| Object | trade paperbacks |
—
|
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: trade paperbacks | Statement: [Girl Genius, hasCollectedEditions, trade paperbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectedEditions Context triple: [Girl Genius, hasCollectedEditions, trade paperbacks]
-
A.
hasCollectedEdition
chosen
Indicates that one entity possesses or maintains a special or curated edition or version of another entity as part of a collection.
-
B.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
C.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
D.
numberOfEditions
Indicates the total count of distinct editions associated with a given entity.
-
E.
hasCanonicalCollectionEdition
Indicates that an entity has a specific edition that is recognized as the authoritative or standard version within a collection.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73449eee88190afa52c4e6ef96baa |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.