Triple
T27638733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simple Machines Forum |
E696532
|
entity |
| Predicate | supportsPolls |
P199154
|
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: [Simple Machines Forum, supportsPolls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPolls Context triple: [Simple Machines Forum, supportsPolls, true]
-
A.
hasPollingSystem
chosen
Indicates that one entity uses, is equipped with, or is governed by a particular polling or voting system.
-
B.
hasNotablePoll
Indicates that there exists a poll associated with the subject that is considered significant or noteworthy in some context.
-
C.
overseenDuringPollsBy
Indicates that an activity, process, or event occurring during polls is supervised, monitored, or managed by a specified overseeing entity.
-
D.
canBePolled
Indicates that an entity is eligible or available to be queried or surveyed for its current state, opinion, or data.
-
E.
pollingModel
Indicates a relationship where one entity periodically checks or requests updated information or status from another entity, rather than receiving it automatically.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: April 27, 2026, 2:25 p.m.