Triple
T17560502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | plpython2u |
E427684
|
entity |
| Predicate | isCreatedWithCommand |
P74463
|
FINISHED |
| Object | CREATE EXTENSION plpython2u |
—
|
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: CREATE EXTENSION plpython2u | Statement: [plpython2u, isCreatedWithCommand, CREATE EXTENSION plpython2u]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCreatedWithCommand Context triple: [plpython2u, isCreatedWithCommand, CREATE EXTENSION plpython2u]
-
A.
firstCreatedUsing
Indicates that one entity was initially produced or brought into existence through the use, application, or involvement of another entity.
-
B.
createdToCommand
Indicates that one entity was brought into existence or established for the specific purpose of exercising authority or control over another entity.
-
C.
createdWith
chosen
Indicates that something was produced, built, or brought into existence using a particular tool, method, material, or resource.
-
D.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
E.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.