Triple
T7278118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hackenbush |
E163079
|
entity |
| Predicate | solvedClass |
P32439
|
FINISHED |
| Object | finite blue-red strings |
—
|
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: finite blue-red strings | Statement: [Hackenbush, solvedClass, finite blue-red strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solvedClass Context triple: [Hackenbush, solvedClass, finite blue-red strings]
-
A.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
B.
commonlySolvedBy
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
C.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
D.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with another entity.
-
E.
supportedClass
chosen
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.