Triple
T1459760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olson database |
E31483
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | PostgreSQL |
E17669
|
NE 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 | Statement: [Olson database, usedBy, PostgreSQL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PostgreSQL Context triple: [Olson database, usedBy, PostgreSQL]
-
A.
PostgreSQL
chosen
PostgreSQL is a powerful open-source relational database management system known for its robustness, extensibility, and strong standards compliance.
-
B.
PostGIS
PostGIS is an open-source spatial database extender that adds robust geographic object support and spatial querying capabilities to PostgreSQL.
-
C.
MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
-
D.
PL/pgSQL
PL/pgSQL is PostgreSQL’s procedural extension of SQL that allows writing stored functions and triggers with control structures like variables, loops, and conditionals.
-
E.
IBM DB2
IBM DB2 is a family of enterprise-grade relational database management systems developed by IBM, widely used for high-performance, scalable data storage and transaction processing across mainframe, distributed, and cloud environments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e786a208190a57c4e1878c66517 |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 8 p.m.