Triple
T9153978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citizendium |
E219661
|
entity |
| Predicate | hasArticleFormat |
P5128
|
FINISHED |
| Object | neutral point of view |
—
|
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: neutral point of view | Statement: [Citizendium, hasArticleFormat, neutral point of view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArticleFormat Context triple: [Citizendium, hasArticleFormat, neutral point of view]
-
A.
hasArticleStructure
Indicates that one entity possesses or follows a specific article-like structural organization (e.g., sections, headings, or layout).
-
B.
containsArticle
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
C.
hasArticleSystem
Indicates that a language or system employs a structured set of articles (such as definite or indefinite markers) as part of its grammar.
-
D.
hasPublishingFormat
chosen
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
-
E.
hasAnthologyFormat
Indicates that an entity is presented or structured in the form of an anthology (a collection of distinct works or pieces).
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96f87ac8190b2fc6d2b2834c1b6 |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.