Triple
T3995398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entscheidungsproblem |
E87086
|
entity |
| Predicate | asksFor |
P2350
|
FINISHED |
| Object | general algorithm for deciding validity of first-order logic statements |
—
|
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: general algorithm for deciding validity of first-order logic statements | Statement: [Entscheidungsproblem, asksFor, general algorithm for deciding validity of first-order logic statements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asksFor Context triple: [Entscheidungsproblem, asksFor, general algorithm for deciding validity of first-order logic statements]
-
A.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
B.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
C.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
D.
callsFor
chosen
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
requiresFinding
Indicates that one entity’s validity, execution, or completion is contingent upon a specific finding or determination being made about 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.