Triple
T15889244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Böhm–Jacopini theorem |
E385272
|
entity |
| Predicate | coreConstruct |
P120949
|
FINISHED |
| Object | sequence |
—
|
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: sequence | Statement: [Böhm–Jacopini theorem, coreConstruct, sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreConstruct Context triple: [Böhm–Jacopini theorem, coreConstruct, sequence]
-
A.
constructs
Indicates that an agent builds, creates, or assembles something, typically resulting in a new or more complex entity or structure.
-
B.
constructedTo
Indicates that one entity has been built, created, or designed for the purpose of serving, supporting, or enabling another entity.
-
C.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
D.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
E.
constructedUnder
Indicates that something was built, created, or assembled while subject to the authority, direction, or conditions imposed by a particular agent, rule, plan, or regime.
- F. None of above. chosen
Provenance (4 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.