Triple
T29107903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniRef |
E736815
|
entity |
| Predicate | clusteringMethod |
P150299
|
FINISHED |
| Object | sequence clustering |
—
|
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: sequence clustering | Statement: [UniRef, clusteringMethod, sequence clustering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusteringMethod Context triple: [UniRef, clusteringMethod, sequence clustering]
-
A.
clusterCriterion
chosen
Indicates the rule or condition used to group items together into a cluster based on shared characteristics or similarity.
-
B.
CMeans
Indicates that one concept or entity conveys, expresses, or serves as the means by which another concept or entity is understood or represented.
-
C.
clusterStructure
Indicates that multiple entities are organized into a cluster, specifying how the elements are grouped and related within that clustered arrangement.
-
D.
clusterConcentration
Indicates how densely the elements within a cluster are packed or distributed relative to one another.
-
E.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661bb81b481909690f8617a84cb19 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:16 a.m.