Triple
T25371891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFA |
E632951
|
entity |
| Predicate | acceptsIf |
P52957
|
FINISHED |
| Object | there exists at least one computation path ending in an accepting state |
—
|
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: there exists at least one computation path ending in an accepting state | Statement: [NFA, acceptsIf, there exists at least one computation path ending in an accepting state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsIf Context triple: [NFA, acceptsIf, there exists at least one computation path ending in an accepting state]
-
A.
appliesIf
chosen
Indicates that a rule, condition, or operation is applicable only when certain specified criteria or circumstances are met.
-
B.
laterAccepts
Indicates that one entity accepts, approves, or agrees to something at a time subsequent to a referenced earlier point or event.
-
C.
acceptedFor
Indicates that one entity has been approved or admitted to receive, participate in, or be associated with another entity.
-
D.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
E.
hasAcceptance
Indicates that one entity has formally received, approved, or agreed to something offered, proposed, or requested 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:38 p.m.