Triple
T18628455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamiltonian cycle |
E455347
|
entity |
| Predicate | visitsEachVertex |
P60586
|
FINISHED |
| Object | exactly once |
—
|
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: exactly once | Statement: [Hamiltonian cycle, visitsEachVertex, exactly once]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitsEachVertex Context triple: [Hamiltonian cycle, visitsEachVertex, exactly once]
-
A.
visitorFunction
Indicates a function that is applied to or invoked on each element or node in a structure as part of a visitor-style traversal or processing operation.
-
B.
visits
chosen
Indicates that one entity goes to or spends time at the location or presence of another entity.
-
C.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
-
D.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
E.
hasVisitorFunction
Indicates that an entity is associated with a function or method that implements the Visitor pattern to operate on it.
- 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.