Triple
T28593425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Wikiquote |
E723713
|
entity |
| Predicate | supportsDiscussionOnContent |
P82619
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Persian Wikiquote, supportsDiscussionOnContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiscussionOnContent Context triple: [Persian Wikiquote, supportsDiscussionOnContent, yes]
-
A.
supportsDiscussionOnArticles
chosen
Indicates that an entity enables or facilitates discussion or commenting on articles.
-
B.
containsDiscussionOf
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
C.
supportsCommunityContent
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
D.
supportsTopic
Indicates that one entity provides backing, endorsement, or assistance for a particular topic, idea, or subject.
-
E.
supportsUserTalk
Indicates that one entity provides a platform or mechanism for another entity to engage in user-to-user communication or discussion.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0123d1162c81908182d01ba3ddd236 |
completed | May 11, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_6a01236713d88190b12a567c0dfb2d49 |
completed | May 11, 2026, 12:31 a.m. |
Created at: April 28, 2026, 4:21 a.m.