Triple
T20772707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformers: Generation 1 toys |
E511274
|
entity |
| Predicate | hasCollectorCommunity |
P12098
|
FINISHED |
| Object | Transformers G1 collectors |
—
|
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: Transformers G1 collectors | Statement: [Transformers: Generation 1 toys, hasCollectorCommunity, Transformers G1 collectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectorCommunity Context triple: [Transformers: Generation 1 toys, hasCollectorCommunity, Transformers G1 collectors]
-
A.
hasCollector
Indicates that an entity is associated with, or owned/curated by, a specific collector.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasTargetCommunity
Indicates that something is specifically intended for, directed toward, or designed to serve a particular community or group.
-
D.
hasCraftCommunity
Indicates that an entity is associated with or supports a community engaged in crafting activities.
-
E.
hasCommunityLink
chosen
Indicates that there exists an established connection or association between an entity and a community.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2681ff88190bfe5938c2db6b2c4 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.