Triple
T17519933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | full-stack-fastapi-template |
E426656
|
entity |
| Predicate | databaseComponent |
P95953
|
FINISHED |
| Object | PostgreSQL database |
—
|
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: PostgreSQL database | Statement: [full-stack-fastapi-template, databaseComponent, PostgreSQL database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: databaseComponent Context triple: [full-stack-fastapi-template, databaseComponent, PostgreSQL database]
-
A.
databaseIntroducedIn
Indicates the point in time, version, or context in which a particular database was first introduced or made available.
-
B.
databaseProduct
chosen
Indicates that one entity is a database system that serves as the product or platform associated with another entity.
-
C.
databaseType
Indicates the specific kind or category of database technology associated with an entity.
-
D.
databaseMaintainedBy
Indicates that a particular database is operated, managed, or kept up-to-date by a specified agent or organization.
-
E.
databaseKey
Indicates that one entity serves as a unique key or identifier for accessing or referencing another entity within a database.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.