Triple
T34542788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loomia |
E886845
|
entity |
| Predicate | softwareStackComponent |
P21680
|
FINISHED |
| Object | web.py |
—
|
NE NERFINISHED |
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: web.py | Statement: [Loomia, softwareStackComponent, web.py]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareStackComponent Context triple: [Loomia, softwareStackComponent, web.py]
-
A.
technologyStack
chosen
Indicates the set of technologies, tools, and platforms used together to build or run a system, application, or project.
-
B.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
-
C.
softwareRepository
Indicates that one entity serves as a software code repository or storage location for another entity’s software artifacts or projects.
-
D.
softwareLibrary
Indicates that one entity is a software library that provides code, functionality, or services used by another entity.
-
E.
softwareEngine
Indicates that an entity functions as a software engine, i.e., a core computational or processing component that drives or powers software operations for 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71ff7bc9c81909dd1dc8bf47cba8c |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.