Triple
T19288130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPDR |
E482366
|
entity |
| Predicate | usesReplicationMethod |
P28972
|
FINISHED |
| Object | physical 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: physical replication | Statement: [SPDR, usesReplicationMethod, physical replication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReplicationMethod Context triple: [SPDR, usesReplicationMethod, physical replication]
-
A.
replicationMethod
chosen
Indicates the technique or process by which something is copied, reproduced, or duplicated.
-
B.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
-
C.
replicaOf
Indicates that one entity is an exact or near-exact copy of another entity, preserving its form, structure, or content.
-
D.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
E.
replicationSite
Indicates the location or context in which a replication process occurs or is carried out between entities.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc043fa481909bbe281a70fb508e |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.