Triple
T6459909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelly |
E142090
|
entity |
| Predicate | allowsUserGeneratedContent |
P13367
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jelly, allowsUserGeneratedContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsUserGeneratedContent Context triple: [Jelly, allowsUserGeneratedContent, true]
-
A.
hasUserGeneratedContent
Indicates that the subject contains or is associated with content created directly by users rather than by the system or administrators.
-
B.
contentLicenseAllows
Indicates that a content license grants permission for a specified use or action involving the content.
-
C.
supportsCommunityContent
chosen
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
D.
regulatesContentFor
Indicates that one entity controls, manages, or sets rules governing the content produced, shared, or accessed by another entity.
-
E.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to another entity.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f50ea88190af29c8c249ff2b69 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.