Triple
T31657505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor |
E807896
|
entity |
| Predicate | valueConflict |
P174858
|
FINISHED |
| Object | prioritizes career over romance |
—
|
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: prioritizes career over romance | Statement: [Victor, valueConflict, prioritizes career over romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueConflict Context triple: [Victor, valueConflict, prioritizes career over romance]
-
A.
settingConflict
Indicates a conflict or incompatibility between two settings, configurations, or environmental conditions.
-
B.
featuresConflictType
Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
-
C.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
D.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
-
E.
keyConflictWith
Indicates that one key or identifier is incompatible, collides, or cannot coexist without conflict with another key or identifier.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: April 30, 2026, 10:56 p.m.