Triple
T19992005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sen’s liberal paradox |
E494085
|
entity |
| Predicate | incompatibilityBetween |
P113438
|
FINISHED |
| Object | minimal liberalism |
—
|
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: minimal liberalism | Statement: [Sen’s liberal paradox, incompatibilityBetween, minimal liberalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incompatibilityBetween Context triple: [Sen’s liberal paradox, incompatibilityBetween, minimal liberalism]
-
A.
notCompatibleWith
Indicates that two entities cannot function together properly or are unsuitable for joint use or interaction.
-
B.
featuresConflictType
Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
-
C.
complementarityIssue
Indicates that there is a problem or incompatibility in how two or more entities complement or fit with each other.
-
D.
compatibleStand
Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
-
E.
foundInconsistentWith
chosen
Indicates that one entity has been determined to conflict with, contradict, or fail to align with 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe10ffc81908c94168b0a8ea9c9 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.