Triple
T28594159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean Wikibooks |
E723729
|
entity |
| Predicate | supportsDiscussionPages |
P31864
|
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: [Korean Wikibooks, supportsDiscussionPages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiscussionPages Context triple: [Korean Wikibooks, supportsDiscussionPages, yes]
-
A.
hasDiscussionPages
chosen
Indicates that an entity is associated with one or more pages where discussions or conversations about it take place.
-
B.
supportsUserTalk
Indicates that one entity provides a platform or mechanism for another entity to engage in user-to-user communication or discussion.
-
C.
supportsDiscussionOnArticles
Indicates that an entity enables or facilitates discussion or commenting on articles.
-
D.
hasDiscussionSystem
Indicates that an entity is equipped with or supports a system for facilitating discussions or conversations.
-
E.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
- 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_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
Created at: April 28, 2026, 4:21 a.m.