Triple
T8302337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai Wikinews |
E194376
|
entity |
| Predicate | neutralPointOfViewPolicy |
P66113
|
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: [Thai Wikinews, neutralPointOfViewPolicy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutralPointOfViewPolicy Context triple: [Thai Wikinews, neutralPointOfViewPolicy, yes]
-
A.
isNeutralAbout
Indicates that one entity has no strong positive or negative opinion, preference, or stance toward another entity or subject.
-
B.
notableViewpoints
Indicates that an entity is associated with significant or noteworthy viewpoints, perspectives, or opinions.
-
C.
usesNeutral
Indicates that one entity employs or applies something in a neutral, unbiased, or non-aligned manner toward another entity or context.
-
D.
guaranteedNeutralityOf
chosen
Indicates that one entity ensures and commits to maintaining impartiality or non-involvement of another entity in a given context or interaction.
-
E.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8a45348190a7895b33abcb64c9 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.