Triple
T1289396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isha |
E27509
|
entity |
| Predicate | hasDifferentOpinionsOn |
P28131
|
FINISHED |
| Object | exact start time |
—
|
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: exact start time | Statement: [Isha, hasDifferentOpinionsOn, exact start time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDifferentOpinionsOn Context triple: [Isha, hasDifferentOpinionsOn, exact start time]
-
A.
opinionBy
Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
-
B.
hasLongTermDebateOn
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
-
C.
hasMajorityOpinionBy
Indicates that a majority of the relevant group or decision-making body holds or supports the opinion expressed by the referenced entity.
-
D.
notableOpinion
Indicates that one entity holds a significant or widely recognized opinion or viewpoint about another entity.
-
E.
pluralityOpinionBy
Indicates that the referenced opinion is the controlling or majority view issued by a decision-making body, as opposed to concurring or dissenting opinions.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d4dfb081908c8825d6062b1d99 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:51 p.m.