Triple
T26966784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL |
E679191
|
entity |
| Predicate | acceptanceCondition |
P161385
|
FINISHED |
| Object | existence of an accepting computation path |
—
|
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: existence of an accepting computation path | Statement: [NL, acceptanceCondition, existence of an accepting computation path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptanceCondition Context triple: [NL, acceptanceCondition, existence of an accepting computation path]
-
A.
acceptanceCondition
chosen
Indicates the criteria or circumstances under which something is approved, agreed to, or deemed valid.
-
B.
rejectionCondition
Indicates the condition or set of criteria under which something (such as a request, offer, or item) is deemed unacceptable and therefore refused or discarded.
-
C.
supportsCondition
Indicates that one entity helps maintain, enable, or is compatible with a particular condition or state in another entity.
-
D.
hasAcceptance
Indicates that one entity has formally received, approved, or agreed to something offered, proposed, or requested by another entity.
-
E.
appointmentCondition
Indicates the specific terms, requirements, or circumstances that must be met or that apply for an appointment to be scheduled, valid, or carried out.
- 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_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:36 a.m.