Triple
T36467464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RLISP |
E898458
|
entity |
| Predicate | hasControlStructures |
P120951
|
FINISHED |
| Object | conditionals |
—
|
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: conditionals | Statement: [RLISP, hasControlStructures, conditionals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlStructures Context triple: [RLISP, hasControlStructures, conditionals]
-
A.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
B.
typicalControlStructures
chosen
Indicates that the subject entity commonly governs or organizes the flow of execution or behavior of the object entity, as a standard or usual control mechanism.
-
C.
hasLoopOrBranch
Indicates that the referenced structure, process, or path contains at least one loop or branching point in its flow or topology.
-
D.
hasCommandStructure
Indicates that one entity possesses an organized hierarchy of authority or control that governs another entity or set of entities.
-
E.
hasControlBranch
Indicates that one entity possesses a controlling or decision-making branch or subdivision within another entity or system.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.