Triple
T15108407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10gen |
E360846
|
entity |
| Predicate | sloganOrPositioning |
P86825
|
FINISHED |
| Object | alternative to relational databases |
—
|
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: alternative to relational databases | Statement: [10gen, sloganOrPositioning, alternative to relational databases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganOrPositioning Context triple: [10gen, sloganOrPositioning, alternative to relational databases]
-
A.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
B.
sloganScope
Indicates the contextual scope or domain within which a particular slogan is intended to apply or be used.
-
C.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
D.
sloganForm
chosen
Indicates that one entity serves as the slogan or advertising catchphrase associated with another entity.
-
E.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058af8988190977d998f85893836 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.