Triple
T32706982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabin automaton |
E836299
|
entity |
| Predicate | hasAcceptanceCondition |
P161385
|
FINISHED |
| Object | Rabin acceptance condition |
—
|
NE NERFINISHED |
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: Rabin acceptance condition | Statement: [Rabin automaton, hasAcceptanceCondition, Rabin acceptance condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcceptanceCondition Context triple: [Rabin automaton, hasAcceptanceCondition, Rabin acceptance condition]
-
A.
acceptanceCondition
chosen
Indicates the criteria or circumstances under which something is approved, agreed to, or deemed valid.
-
B.
hasAcceptance
Indicates that one entity has formally received, approved, or agreed to something offered, proposed, or requested by another entity.
-
C.
mandatedAcceptanceOf
Indicates that one entity is required, by rule or authority, to accept or approve something from another entity.
-
D.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
E.
canCondition
Indicates that one entity has the capability or potential to impose, apply, or bring about a particular condition on another entity or situation.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 1:10 a.m.