Triple
T28330169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codership |
E717516
|
entity |
| Predicate | implementsInProducts |
P22535
|
FINISHED |
| Object | virtually synchronous replication |
—
|
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: virtually synchronous replication | Statement: [Codership, implementsInProducts, virtually synchronous replication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementsInProducts Context triple: [Codership, implementsInProducts, virtually synchronous replication]
-
A.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
B.
implementedOn
chosen
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
C.
hasProduct
Indicates that an entity possesses, offers, or is associated with a particular product.
-
D.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
-
E.
usesProductFrom
Indicates that one entity makes use of or employs a product that originates from or is provided 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:31 a.m.