Triple

T17560523
Position Surface form Disambiguated ID Type / Status
Subject plpython2u E427684 entity
Predicate supportsDataExchange P127948 FINISHED
Object mapping between PostgreSQL types and Python types 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: mapping between PostgreSQL types and Python types | Statement: [plpython2u, supportsDataExchange, mapping between PostgreSQL types and Python types]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsDataExchange
Context triple: [plpython2u, supportsDataExchange, mapping between PostgreSQL types and Python types]
  • A. exchangeType
    Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
  • B. supportsInterconnection
    Indicates that one entity enables, facilitates, or maintains a connection or interoperability between two or more other entities.
  • C. supportsChannels
    Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
  • D. supportsShares
    Indicates that one entity provides assistance, endorsement, or resources to another entity in the context of shared ownership, shared resources, or jointly held interests.
  • E. supportedProtocol
    Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e456267e208190a1238fbe1a535bb0 completed April 19, 2026, 4:12 a.m.
PD Predicate disambiguation batch_69e3b4fb39948190a82a597c5bac5c57 completed April 18, 2026, 4:44 p.m.
PDg Predicate description generation batch_69e3bbb50b448190a59dd4be33c76db7 completed April 18, 2026, 5:13 p.m.
Created at: April 10, 2026, 5:50 a.m.