Triple
T3478165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curry paradox |
E73424
|
entity |
| Predicate | canBeBlockedBy |
P43618
|
FINISHED |
| Object | rejecting contraction |
—
|
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: rejecting contraction | Statement: [Curry paradox, canBeBlockedBy, rejecting contraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBlockedBy Context triple: [Curry paradox, canBeBlockedBy, rejecting contraction]
-
A.
canBlock
chosen
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
-
B.
canBeBlockedWhenLost
Indicates that an item, once lost, is capable of being deactivated or blocked to prevent further use or access.
-
C.
canBeSeizedBy
Indicates that one entity is legally or physically able to be taken control of, captured, or confiscated by another entity.
-
D.
belongsToBlock
Indicates that something is a member or component of a specific block or grouping.
-
E.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb5b7584819096eadd1c5268eab1 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.