Triple
T18628471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamiltonian cycle |
E455347
|
entity |
| Predicate | decisionProblem |
P132452
|
FINISHED |
| Object | Hamiltonian cycle problem |
—
|
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: Hamiltonian cycle problem | Statement: [Hamiltonian cycle, decisionProblem, Hamiltonian cycle problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionProblem Context triple: [Hamiltonian cycle, decisionProblem, Hamiltonian cycle problem]
-
A.
decisionMakingTool
Indicates that an entity functions as a tool or system used to support, structure, or carry out decision-making processes for another entity.
-
B.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
C.
decisionMakingModel
Indicates a relationship where an entity uses or is associated with a specific model or framework for making decisions.
-
D.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
-
E.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f063a1c819087e544c64f5cf80f |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.