Triple
T32414589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Core (SQL) API |
E828305
|
entity |
| Predicate | hasDataModelConcept |
P531
|
FINISHED |
| Object | 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: database | Statement: [Core (SQL) API, hasDataModelConcept, database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataModelConcept Context triple: [Core (SQL) API, hasDataModelConcept, database]
-
A.
hasConceptualStructure
Indicates that one entity embodies, organizes, or is characterized by a particular conceptual structure defined by another entity.
-
B.
hasImplementedConcept
Indicates that an entity has put a particular concept into practice or realized it in an implemented form.
-
C.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
D.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
E.
dataModelSupport
Indicates that one entity provides compatibility with, or is capable of operating using, the data model defined or required by 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:53 a.m.