Triple
T9565258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amanda |
E230773
|
entity |
| Predicate | hasOppositeMeaningTo |
P21665
|
FINISHED |
| Object | unlovable |
—
|
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: unlovable | Statement: [Amanda, hasOppositeMeaningTo, unlovable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppositeMeaningTo Context triple: [Amanda, hasOppositeMeaningTo, unlovable]
-
A.
hasConceptualOpposite
chosen
Indicates that one entity represents a concept that is fundamentally opposed or contrary in meaning to the concept represented by another entity.
-
B.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
-
C.
isOppositionCounterpartOf
Indicates a relationship where one entity serves as the opposing or counterpart force, side, or position to another within a conflict, competition, or contrast.
-
D.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
E.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd996a01b081908e2782f41520f73d |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.