Triple
T22876303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbit compiler |
E567334
|
entity |
| Predicate | paradigmTargeted |
P150093
|
FINISHED |
| Object | functional programming |
—
|
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: functional programming | Statement: [Rabbit compiler, paradigmTargeted, functional programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paradigmTargeted Context triple: [Rabbit compiler, paradigmTargeted, functional programming]
-
A.
targetedRegime
Indicates that an entity intentionally directed actions, policies, or operations against a particular governing regime.
-
B.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
C.
plannedTarget
Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
-
D.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
E.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f58a7308190b710bdf013e2e114 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:39 p.m.