Triple
T26966764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL |
E679191
|
entity |
| Predicate | completeProblem |
P22418
|
FINISHED |
| Object | directed s-t reachability |
—
|
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: directed s-t reachability | Statement: [NL, completeProblem, directed s-t reachability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completeProblem Context triple: [NL, completeProblem, directed s-t reachability]
-
A.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
-
B.
solved
chosen
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
C.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
D.
completeFor
Indicates that one entity finishes, fulfills, or brings to conclusion a task, requirement, or process on behalf of another entity.
-
E.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 6:36 a.m.