Triple
T18628485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamiltonian cycle |
E455347
|
entity |
| Predicate | exampleGraphWithout |
P28211
|
FINISHED |
| Object | tree with more than two vertices |
—
|
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: tree with more than two vertices | Statement: [Hamiltonian cycle, exampleGraphWithout, tree with more than two vertices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleGraphWithout Context triple: [Hamiltonian cycle, exampleGraphWithout, tree with more than two vertices]
-
A.
usesGraphType
Indicates that one entity employs or is configured to operate with a specific type of graph representation or graph model.
-
B.
graphAnalogue
Indicates that one entity serves as a graph-theoretic counterpart or structural analogue of another entity.
-
C.
graphNameCanBe
Indicates that a graph is allowed to take on or be assigned a specified name.
-
D.
nonExample
chosen
Indicates that something is explicitly identified as not being an example or instance of a given concept, category, or pattern.
-
E.
graphics
Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
- 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.