Triple
T4325439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flask-SQLAlchemy |
E96623
|
entity |
| Predicate | initialReleaseApprox |
P56255
|
FINISHED |
| Object | around 2009 |
—
|
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: around 2009 | Statement: [Flask-SQLAlchemy, initialReleaseApprox, around 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialReleaseApprox Context triple: [Flask-SQLAlchemy, initialReleaseApprox, around 2009]
-
A.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
B.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
C.
initialReleaseDeveloper
Indicates that the subject entity is the developer responsible for the initial release of the object entity.
-
D.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
E.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3512ec18481908a7b5c29b3902b53 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:13 p.m.