Triple
T26966580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post correspondence problem |
E679187
|
entity |
| Predicate | boundedVariant |
P4680
|
FINISHED |
| Object | NP-complete |
—
|
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: NP-complete | Statement: [Post correspondence problem, boundedVariant, NP-complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundedVariant Context triple: [Post correspondence problem, boundedVariant, NP-complete]
-
A.
boundedByApprox
Indicates that one quantity is constrained by another within an approximate or tolerance-based bound, rather than an exact strict limit.
-
B.
variant
chosen
Indicates that one entity is an alternative form, version, or variation of another entity.
-
C.
boundIs
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
-
D.
boundedSuperiorlyBy
Indicates that one entity serves as the upper or top boundary limit of another entity.
-
E.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621210b788190ab9e910cd635f366 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:36 a.m.