Triple

T17559568
Position Surface form Disambiguated ID Type / Status
Subject MariaDB Corporation E427663 entity
Predicate competesWith P1375 FINISHED
Object PostgreSQL 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: PostgreSQL | Statement: [MariaDB Corporation, competesWith, PostgreSQL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PostgreSQL
Context triple: [MariaDB Corporation, competesWith, PostgreSQL]
  • A. PostgreSQL chosen
    PostgreSQL is a powerful open-source relational database management system known for its robustness, extensibility, and strong standards compliance.
  • B. Greenplum
    Greenplum is a massively parallel, open-source data warehouse and analytics platform designed for large-scale business intelligence and big data workloads.
  • C. PostgreSQL documentation
    PostgreSQL documentation is the official, comprehensive reference and user guide for the PostgreSQL relational database system, covering its features, configuration, and extensions.
  • D. PolarDB
    PolarDB is a cloud-native relational database service developed by Alibaba Cloud that provides high performance, scalability, and compatibility with popular database engines.
  • E. PostGIS
    PostGIS is an open-source spatial database extender that adds robust geographic object support and spatial querying capabilities to PostgreSQL.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e4562573e48190a19f30fe915a5455 completed April 19, 2026, 4:12 a.m.
Created at: April 10, 2026, 5:50 a.m.