Triple
T9932034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDS (Child DS) |
E192668
|
entity |
| Predicate | semanticsSimilarTo |
P3575
|
FINISHED |
| Object | DS (Delegation Signer) record |
—
|
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: DS (Delegation Signer) record | Statement: [CDS (Child DS), semanticsSimilarTo, DS (Delegation Signer) record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticsSimilarTo Context triple: [CDS (Child DS), semanticsSimilarTo, DS (Delegation Signer) record]
-
A.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
B.
moreSimilarTo
Indicates that one entity bears a greater degree of similarity to a second entity than to a third entity, according to some defined similarity measure.
-
C.
hasGrammaticalSimilarityTo
Indicates that two linguistic elements share similar grammatical structure, form, or function.
-
D.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
E.
synonym
chosen
Indicates that two terms have the same or nearly the same meaning in a given context.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.