Triple
T14891251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iStockphoto |
E359757
|
entity |
| Predicate | hasContributorCommunity |
P92491
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [iStockphoto, hasContributorCommunity, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContributorCommunity Context triple: [iStockphoto, hasContributorCommunity, global]
-
A.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
-
D.
hasComponentCommunity
chosen
Indicates that an entity includes or is composed of a specific community as one of its constituent parts.
-
E.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f883288190af602633fa7d6860 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 2:10 a.m.