Triple
T14439357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClearCase |
E358045
|
entity |
| Predicate | supportsReplication |
P28972
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ClearCase, supportsReplication, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReplication Context triple: [ClearCase, supportsReplication, yes]
-
A.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
-
B.
replicationMethod
chosen
Indicates the technique or process by which something is copied, reproduced, or duplicated.
-
C.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
D.
supportsRedundancy
Indicates that one entity provides or enables backup or failover capabilities for another to ensure continued operation if a primary component fails.
-
E.
supportsBackupCopy
Indicates that one entity provides the capability or functionality to create, maintain, or use a backup copy of 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914c1398819090fa2a74d257ba3e |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.