Triple
T9602561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comic Clubs |
E231883
|
entity |
| Predicate | typicalMemberIs |
P2776
|
FINISHED |
| Object | comic book enthusiast |
—
|
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: comic book enthusiast | Statement: [Comic Clubs, typicalMemberIs, comic book enthusiast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMemberIs Context triple: [Comic Clubs, typicalMemberIs, comic book enthusiast]
-
A.
typicalMembers
chosen
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
B.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
C.
membershipCharacteristic
Indicates that an entity possesses a specific attribute or quality by virtue of its membership in a particular group or category.
-
D.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
E.
eachMemberHas
Indicates that every individual element within a group or collection possesses or is associated with a specified property, attribute, or item.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5af8f0819089408ed630afa812 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.