Triple
T18628488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamiltonian cycle |
E455347
|
entity |
| Predicate | edgeConstraint |
P49586
|
FINISHED |
| Object | uses only edges of the graph |
—
|
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: uses only edges of the graph | Statement: [Hamiltonian cycle, edgeConstraint, uses only edges of the graph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeConstraint Context triple: [Hamiltonian cycle, edgeConstraint, uses only edges of the graph]
-
A.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
B.
designedToConstrain
chosen
Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
-
C.
inclinationConstraint
Indicates a restriction or condition placed on the allowable angle or tilt between entities or components.
-
D.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
E.
typicalEdge
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
- 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_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. |
Created at: April 10, 2026, 11:46 a.m.