Triple
T26192910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogden v. Saunders |
E655014
|
entity |
| Predicate | hasOpinionCount |
P167742
|
FINISHED |
| Object | multiple separate opinions |
—
|
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: multiple separate opinions | Statement: [Ogden v. Saunders, hasOpinionCount, multiple separate opinions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpinionCount Context triple: [Ogden v. Saunders, hasOpinionCount, multiple separate opinions]
-
A.
hasOpinionSection
Indicates that something includes or is associated with a dedicated opinion section.
-
B.
hasDifferentOpinionsOn
Indicates that two or more entities hold differing views or judgments regarding a particular topic, issue, or subject.
-
C.
voteCount
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
D.
compiledOpinionsOf
Indicates that one entity has gathered, organized, or synthesized the opinions of another entity or group into a collective form.
-
E.
givesOpinionOn
Indicates that one entity expresses a view, judgment, or evaluation about another entity or subject.
- F. None of above. chosen
Provenance (4 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 26, 2026, 8:45 p.m.